package sbt.testing;

public enum Status 
{
	Success, Error, Failure, Skipped
}



@@ -15,16 +15,1466 @@
 sting;%0A%0A
+/**%0A * Represents the status of running a test. Test frameworks can decided which of these to%0A * use and what they mean, but in general, the intended meanings are:%0A *%0A * %3Cul%3E%0A * %3Cli%3ESuccess - a test succeeded%3C/li%3E%0A * %3Cli%3EError - an unexpected error (as opposed to an assertion error) occurred during a test%3C/li%3E%0A * %3Cli%3EFailure - an assertion failed during a test%3C/li%3E%0A * %3Cli%3ESkipped - a test was skipped for any reason%3C/li%3E%0A * %3Cli%3EIgnored - a test was ignored, %3Cem%3Ei.e.%3C/em%3E, temporarily disabled with the intention of fixing it later%3C/li%3E%0A * %3Cli%3ECanceled - a test was canceled, %3Cem%3Ei.e.%3C/em%3E, not able to be completed because of some unmet pre-condition, such as a database being offline that the test requires%3C/li%3E%0A * %3Cli%3EPending - a test was declared as pending, %3Cem%3Ei.e.%3C/em%3E, with test code and/or production code as yet unimplemented %3C/li%3E%0A * %3C/ul%3E%0A *%0A * %3Cp%3E%0A * JUnit and specs2 differentiate between errors and failures. ScalaTest reports everything (both assertion failures and unexpected errors) as failures.%0A * JUnit and ScalaTest support ignored tests. ScalaTest and specs2 support a notion of pending tests. ScalaTest differentiates between ignored and%0A * canceled tests, whereas specs2 only supports skipped tests, which are implemented like ScalaTest's canceled tests. TestNG uses %22skipped%22 to report tests%0A * that were not executed because of failures in dependencies, which is also similar to canceled tests in ScalaTest.%0A * %3C/p%3E%0A */%0A
 public e
@@ -1520,13 +1520,41 @@
  Skipped
+, Ignored, Canceled, Pending
 %0A%7D%0A%0A%0A

Add Pending, Canceled, Ignored to Status enum.