Skip to content
This repository has been archived by the owner on Jun 12, 2021. It is now read-only.

Can I use xBehave.net with continuous test tools?

Jump to bottom
Mo Valipour edited this page Sep 21, 2015 · 5 revisions

NCrunch

NCrunch works fine with xBehave.net, however there are a few things to note:

  • There is a minor coverage indicator issue when a scenario has a failing step. The coverage indicators are still readable and the line which is the source of the exception is highlighted correctly, but there are some extraneous failure indicators in non-failing steps.

  • Also bear in-mind that given NCrunch separates the discovery and execution of tests, it is unable to show you the correct number of XBehave tests/steps. -- i.e. it regards every scenario as one tests.

We regard these as minor annoyances and we do not hesitate to recommend the use of NCrunch with xBehave.net.

ContinuousTests a.k.a MightyMoose a.k.a AutoTest

YMMV. Adding a vanilla xUnit.test (see NCrunch) seemed to at least partially allow CT/MM/AT to recognise the assembly but it then seemed to get confused by the coverage indicated by the xBehave.net scenarios. There seem to be issues to address in CT/MM/AT before it is useable with xBehave.net. At the time of writing it is not recommended to use CT/MM/AT with xBehave.net.

Clone this wiki locally