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
canEqual
(arg0: Any): Boolean
-
def
clone
(): AnyRef
-
def
eq
(arg0: AnyRef): Boolean
-
def
equals
(arg0: Any): Boolean
-
def
finalize
(): Unit
-
def
getClass
(): java.lang.Class[_]
-
def
hashCode
(): Int
-
def
isInstanceOf
[T0]
: Boolean
-
def
ne
(arg0: AnyRef): Boolean
-
def
notify
(): Unit
-
def
notifyAll
(): Unit
-
def
productArity
: Int
-
def
productElement
(arg0: Int): Any
-
def
productIterator
: Iterator[Any]
-
def
productPrefix
: String
-
def
readResolve
(): AnyRef
-
def
synchronized
[T0]
(arg0: ⇒ T0): T0
-
def
toString
(): String
-
def
wait
(): Unit
-
def
wait
(arg0: Long, arg1: Int): Unit
-
def
wait
(arg0: Long): Unit
-
def
productElements
: Iterator[Any]
Inherited from Serializable
Inherited from Serializable
Inherited from Product
Inherited from Equals
Inherited from AnyRef
Inherited from Any
A
Formatter
that indicates reporters may wish to suppress reporting of anEvent
. "Suppress" means that the event won't be reported to the user.An example is that specification-style suites, such as
FunSpec
, generate output that reads more like a specification. One aspect of this is that generally only a single event should be reported for each test, so that output can appear like this:ScalaTest suites should generate two events per test, a
TestStarting
event and either aTestSucceeded
or aTestFailed
event. TheFunSpec
trait does report both events, but passes aMotionToSuppress
along with theTestStarting
event. As a result, TheTestStarting
events have no effect on the output. EachTestSucceeded
orTestFailed
event, which is sent with anIndentedText
formatter instead of aMotionToSuppress
, will generate output, such as "- should be empty
".Reporters may choose to ignore a
MotionToSuppress
. For example, an XML reporter may want to report everything about every event that is fired during a concurrent run, so that the events can be reordered later by reading the complete, but unordered, information from an XML file. In this case, the XML reporter would actually report events that were fired with aMotionToSuppress
, including indicating that the report included a motion to suppress.