Create a JUnitTestFailedError with the specified stack depth, detail
message, and cause.
Create a JUnitTestFailedError with the specified stack depth, detail
message, and cause.
Note that the detail message associated with cause is not automatically incorporated in this throwable's detail message.
A detail message for this JUnitTestFailedError.
the cause, the Throwable that caused this JUnitTestFailedError to be thrown.
the depth in the stack trace of this exception at which the line of test code that failed resides.
Create a JUnitTestFailedError with the specified stack depth and cause.
Create a JUnitTestFailedError with the specified stack depth and cause. The
message field of this exception object will be initialized to
if (cause.getMessage == null) "" else cause.getMessage.
the cause, the Throwable that caused this JUnitTestFailedError to be thrown.
the depth in the stack trace of this exception at which the line of test code that failed resides.
Create a JUnitTestFailedError with a specified stack depth and detail message.
Create a JUnitTestFailedError with a specified stack depth and detail message.
A detail message for this JUnitTestFailedError.
the depth in the stack trace of this exception at which the line of test code that failed resides.
Create a JUnitTestFailedError with specified stack depth and no detail message or cause.
Create a JUnitTestFailedError with specified stack depth and no detail message or cause.
the depth in the stack trace of this exception at which the line of test code that failed resides.
an optional detail message for this TestFailedException.
an optional cause, the Throwable that caused this TestFailedException to be thrown.
the depth in the stack trace of this exception at which the line of test code that failed resides.
Indicates whether this object can be equal to the passed object.
an optional cause, the Throwable that caused this TestFailedException to be thrown.
an optional cause, the Throwable that caused this TestFailedException to be thrown.
Indicates whether this object is equal to the passed object.
Indicates whether this object is equal to the passed object. If the passed object is
a JUnitTestFailedError, equality requires equal message,
cause, and failedCodeStackDepth fields, as well as equal
return values of getStackTrace.
A string that provides the filename of the line of code that failed, suitable
for presenting to a user, which is taken from this exception's StackTraceElement at the depth specified
by failedCodeStackDepth.
A string that provides the filename of the line of code that failed, suitable
for presenting to a user, which is taken from this exception's StackTraceElement at the depth specified
by failedCodeStackDepth.
This is a def instead of a val because exceptions are mutable: their stack trace can
be changed after the exception is created. This is done, for example, by the SeveredStackTraces trait.
a string containing the filename that caused the failed test
A string that provides the filename and line number of the line of code that failed, suitable
for presenting to a user, which is taken from this exception's StackTraceElement at the depth specified
by failedCodeStackDepth.
A string that provides the filename and line number of the line of code that failed, suitable
for presenting to a user, which is taken from this exception's StackTraceElement at the depth specified
by failedCodeStackDepth.
This is a def instead of a val because exceptions are mutable: their stack trace can
be changed after the exception is created. This is done, for example, by the SeveredStackTraces trait.
a user-presentable string containing the filename and line number that caused the failed test
A string that provides the line number of the line of code that failed, suitable
for presenting to a user, which is taken from this exception's StackTraceElement at the depth specified
by failedCodeStackDepth.
A string that provides the line number of the line of code that failed, suitable
for presenting to a user, which is taken from this exception's StackTraceElement at the depth specified
by failedCodeStackDepth.
This is a def instead of a val because exceptions are mutable: their stack trace can
be changed after the exception is created. This is done, for example, by the SeveredStackTraces trait.
a string containing the line number that caused the failed test
the depth in the stack trace of this exception at which the line of test code that failed resides.
the depth in the stack trace of this exception at which the line of test code that failed resides.
Returns a hash code value for this object.
Returns a hash code value for this object.
an optional detail message for this TestFailedException.
an optional detail message for this TestFailedException.
Returns an instance of this exception's class, identical to this exception,
except with the detail message option string replaced with the result of passing
the current detail message to the passed function, fun.
Returns an instance of this exception's class, identical to this exception,
except with the detail message option string replaced with the result of passing
the current detail message to the passed function, fun.
A function that, given the current optional detail message, will produce
the modified optional detail message for the result instance of TestFailedException.
Returns an exception of class JUnitTestFailedError with failedExceptionStackDepth set to 0 and
all frames above this stack depth severed off.
Returns an exception of class JUnitTestFailedError with failedExceptionStackDepth set to 0 and
all frames above this stack depth severed off. This can be useful when working with tools (such as IDEs) that do not
directly support ScalaTest. (Tools that directly support ScalaTest can use the stack depth information delivered
in the StackDepth exceptions.)
Exception that indicates a test failed.
The purpose of this exception is to encapsulate the same stack depth information provided by
TestFailedException, which is used when running with ScalaTest, but be reported as a failure not an error when running with JUnit. The stack depth information indicates which line of test code failed, so that when running with ScalaTest information can be presented to the user that makes it quick to find the failing line of test code. (In other words, when running with ScalaTest the user need not scan through the stack trace to find the correct filename and line number of the failing test.)JUnit distinguishes between failures and errors. If a test fails because of a failed assertion, that is considered a failure in JUnit. If a test fails for any other reason, either the test code or the application being tested threw an unexpected exception, that is considered an error in JUnit. This class differs from
TestFailedExceptionin that it extendsjunit.framework.AssertionFailedError. Instances of this class are thrown by the assertions provided byAssertionsForJUnit, and matcher expressions provided byShouldMatchersForJUnit, andMustMatchersForJUnit.The way JUnit 3 (JUnit 3.8 and earlier releases) decided whether an exception represented a failure or error is that only thrown
junit.framework.AssertionFailedErrors were considered failures. Any other exception type was considered an error. The exception type thrown by the JUnit 3 assertion methods declared injunit.framework.Assert(such asassertEquals,assertTrue, andfail) was, therefore,AssertionFailedError. In JUnit 4,AssertionFailedErrorwas made to extendjava.lang.AssertionError, and the distinction between failures and errors was essentially dropped. However, some tools that integrate with JUnit carry on this distinction, so even if you are using JUnit 4 you may want to use the "ForJUnit" of ScalaTest assertions and matchers.