Hi,
I have some tests (integration tests incorporating WCF and AppDomains) that do not work when a test runner is reused for more than one test.
Thus it would be nice if I could specify for these tests "Terminate Test Runner Tasks When All Test Execution Is Complete".
It could be specified either as an attribute or as a project level configuration.
Currently this can only be specified for the complete NCrunch configuration.
Regards
Wilhelm
PS: NCrunch 2.4 works really nice.
Feature Suggestions
Attribute for "Terminate Test Runner Tasks When All Test Execution Is Complete"
Started by wilhelmmedetz on 10,239 views
Remco NCrunch Developer
#5322
14 Feb 2014 12:00 UTC
Hi Wilhelm -
Thanks for sharing this request! I'm wondering if you've had a look at the Isolated attribute? I think this may be what you're after.
Cheers,
Remco
Thanks for sharing this request! I'm wondering if you've had a look at the Isolated attribute? I think this may be what you're after.
Cheers,
Remco
Hi Remco,
Thanks for the quick answer.
I am already using the Isolated attribute - but it did not help.
Regards
Wilhelm
Thanks for the quick answer.
I am already using the Isolated attribute - but it did not help.
Regards
Wilhelm
Remco NCrunch Developer
#5329
14 Feb 2014 23:39 UTC
Hi Wilhelm -
IsolatedAttribute is reliable in producing and tearing down specialised test processes for single execution runs. If your tests are still failing intermittently, I suspect there may be something else going on. Do the tests make use of any external resource? A database perhaps?
IsolatedAttribute is reliable in producing and tearing down specialised test processes for single execution runs. If your tests are still failing intermittently, I suspect there may be something else going on. Do the tests make use of any external resource? A database perhaps?
Post a reply
Log in to reply.