Instance Constructors
-
new
TestPendingException
()
Value Members
-
def
!=
(arg0: AnyRef): Boolean
-
def
!=
(arg0: Any): Boolean
-
def
##
(): Int
-
def
==
(arg0: AnyRef): Boolean
-
def
==
(arg0: Any): Boolean
-
def
asInstanceOf
[T0]
: T0
-
def
clone
(): AnyRef
-
def
eq
(arg0: AnyRef): Boolean
-
def
equals
(arg0: Any): Boolean
-
def
fillInStackTrace
(): Throwable
-
def
finalize
(): Unit
-
def
getCause
(): Throwable
-
def
getClass
(): java.lang.Class[_]
-
def
getLocalizedMessage
(): String
-
def
getMessage
(): String
-
def
getStackTrace
(): Array[StackTraceElement]
-
def
hashCode
(): Int
-
def
initCause
(arg0: Throwable): Throwable
-
def
isInstanceOf
[T0]
: Boolean
-
def
ne
(arg0: AnyRef): Boolean
-
def
notify
(): Unit
-
def
notifyAll
(): Unit
-
def
printStackTrace
(arg0: PrintWriter): Unit
-
def
printStackTrace
(arg0: PrintStream): Unit
-
def
printStackTrace
(): Unit
-
def
setStackTrace
(arg0: Array[StackTraceElement]): Unit
-
def
synchronized
[T0]
(arg0: ⇒ T0): T0
-
def
toString
(): String
-
def
wait
(): Unit
-
def
wait
(arg0: Long, arg1: Int): Unit
-
def
wait
(arg0: Long): Unit
Inherited from RuntimeException
Inherited from Exception
Inherited from Throwable
Inherited from Serializable
Inherited from AnyRef
Inherited from Any
Exception thrown to indicate a test is pending.
A pending test is one that has been given a name but is not yet implemented. The purpose of pending tests is to facilitate a style of testing in which documentation of behavior is sketched out before tests are written to verify that behavior (and often, the before the behavior of the system being tested is itself implemented). Such sketches form a kind of specification of what tests and functionality to implement later.
To support this style of testing, a test can be given a name that specifies one bit of behavior required by the system being tested. The test can also include some code that sends more information about the behavior to the reporter when the tests run. At the end of the test, it can call method
pending
, which will cause it to complete abruptly withTestPendingException
. Because tests in ScalaTest can be designated as pending withTestPendingException
, both the test name and any information sent to the reporter when running the test can appear in the report of a test run. (In other words, the code of a pending test is executed just like any other test.) However, because the test completes abruptly withTestPendingException
, the test will be reported as pending, to indicate the actual test, and possibly the functionality, has not yet been implemented.