Create a JUnitTestFailedError
with the specified stack depth, detail
message, and cause.
Create a JUnitTestFailedError
with the specified stack depth and cause.
Create a JUnitTestFailedError
with a specified stack depth and detail message.
Create a JUnitTestFailedError
with specified stack depth and no detail message or cause.
Indicates whether this object can be equal to the passed object.
An optional cause, the Throwable
that caused this StackDepth
exception to be thrown.
Indicates whether this object is equal to the passed object.
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
.
val
failedCodeStackDepth: Int
The depth in the stack trace of this exception at which the line of test code that failed resides.
def
fillInStackTrace(): Throwable
def
getCause(): Throwable
def
getLocalizedMessage(): String
def
getMessage(): String
def
getStackTrace(): Array[StackTraceElement]
def
hashCode(): Int
Returns a hash code value for this object.
def
initCause(throwable: Throwable): Throwable
val
message: Option[String]
An optional detail message for this StackDepth
exception.
def
modifyMessage(fun: (Option[String]) ⇒ Option[String]): JUnitTestFailedError
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
.
def
printStackTrace(arg0: PrintWriter): Unit
def
printStackTrace(arg0: PrintStream): Unit
def
printStackTrace(): Unit
def
setStackTrace(arg0: Array[StackTraceElement]): Unit
def
severedAtStackDepth: JUnitTestFailedError
Returns an exception of class JUnitTestFailedError
with failedExceptionStackDepth
set to 0 and
all frames above this stack depth severed off.
def
toString(): String
Returns a string representation of the object.
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
TestFailedException
in 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.AssertionFailedError
s 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,AssertionFailedError
was 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.authors:
Bill Venners