Hot answers tagged nunit
6
As a general rule of thumb, everytime a test fails or has an indeterminate outcome it requires investigation. If you ignore a failing/indeterminate test then you increase the risk of missing or overlooking a bug.
The value of automation is to execute tests that we deem important enough that we want to run them repeatitively, or tests that are executed more ...
1
We also have same issue in our production monitoring automation suite. To solve this problem to some extent, whenever a test is failed it is marked as INTERMITTENT and same test is repeated for max. 3 times or until it is passed. If it is getting passed in any one of next repetition then issue is left as Intermittent and not alerted. If it is failing all the ...
1
I have a somewhat similar setup, however we decouple our non unit tests (Anything requiring an install to a server) from the typical unit tests which can run directly on the team city build server. In my solution we created a windows service polling team city for new builds via the rest API and when we find a new build we add it to the queue to execute our ...
1
The EventListener is the way to go. However there is a knack: the UnhandledException will not be fired when an Assertion in your test fails. Rather use the TestFinished event to handle failed tests:
public void TestFinished(TestResult result)
{
if (result.Executed && result.IsFailure)
{
Console.WriteLine(string.Format("Failure in ...
Only top voted, non community-wiki answers of a minimum length are eligible
