Can I use xWellBehaved.net with continuous test tools

NCrunch

NCrunch works fine with xBehave.net, so we assume the same for xWellBehaved.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 and is therefore unable to show a separate indicator for each step within a scenario, regarding each scenario, including all examples, as a single test.

We consider these as minor annoyances and we do not hesitate to recommend the use of NCrunch with xWellBehaved.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 recognize 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.

Again, since xWellBehaved.net is a derivative of the xBehave.net baseline, we assume that these same experiences hold true. Let us just say we have no reason to expect the experience would be any different at the time of this writing.