an Ordinal
that can be used to place this event in order in the context of
other events reported during the same run
a localized name identifying the suite containing the test that is pending, suitable for presenting to the user
a string ID for the suite containing the test that is pending, intended to be unique across all suites in a run
an optional fully qualifed Suite
class name containing the test that is pending
the name of the test that is pending
the text of the test that is pending (may be the test name, or a suffix of the test name)
recorded events in the test.
an optional amount of time, in milliseconds, that was required to run the test that is pending
an optional Formatter
that provides extra information that can be used by reporters in determining
how to present this event to the user
An optional Location
that provides information indicating where in the source code an event originated.
an optional object that can be used to pass custom information to the reporter about the TestPending
event
a name for the Thread
about whose activity this event was reported
a Long
indicating the time this event was reported, expressed in terms of the
number of milliseconds since the standard base time known as "the epoch": January 1, 1970, 00:00:00 GMT
Comparing this
event with the event passed as that
.
Comparing this
event with the event passed as that
. Returns
x, where x < 0 iff this < that, x == 0 iff this == that, x > 0 iff this > that.
the event to compare to this event
an optional amount of time, in milliseconds, that was required to run the test that is pending
an optional Formatter
that provides extra information that can be used by reporters in determining
how to present this event to the user
an optional Formatter
that provides extra information that can be used by reporters in determining
how to present this event to the user
An optional Location
that provides information indicating where in the source code an event originated.
An optional Location
that provides information indicating where in the source code an event originated.
an Ordinal
that can be used to place this event in order in the context of
other events reported during the same run
an Ordinal
that can be used to place this event in order in the context of
other events reported during the same run
an optional object that can be used to pass custom information to the reporter about the TestPending
event
an optional object that can be used to pass custom information to the reporter about the TestPending
event
recorded events in the test.
an optional fully qualifed Suite
class name containing the test that is pending
an optional fully qualifed Suite
class name containing the test that is pending
a string ID for the suite containing the test that is pending, intended to be unique across all suites in a run
a localized name identifying the suite containing the test that is pending, suitable for presenting to the user
the name of the test that is pending
the text of the test that is pending (may be the test name, or a suffix of the test name)
a name for the Thread
about whose activity this event was reported
a name for the Thread
about whose activity this event was reported
a Long
indicating the time this event was reported, expressed in terms of the
number of milliseconds since the standard base time known as "the epoch": January 1, 1970, 00:00:00 GMT
a Long
indicating the time this event was reported, expressed in terms of the
number of milliseconds since the standard base time known as "the epoch": January 1, 1970, 00:00:00 GMT
Event that indicates a test is pending, i.e., it hasn't yet been implemented.
To create instances of this class you may use the factory method. For example, given a report function named
report
, you could fire aTestPending
event like this:The suite class name parameter is optional, because suites in ScalaTest are an abstraction that need not necessarily correspond to one class. Nevertheless, in most cases each suite will correspond to a class, and when it does, the fully qualified name of that class should be reported by passing a
Some
forsuiteClassName
. One use for this bit of information is JUnit integration, because the "name" provided to a JUnitorg.junit.runner.Description
appears to usually include a fully qualified class name by convention.an
Ordinal
that can be used to place this event in order in the context of other events reported during the same runa localized name identifying the suite containing the test that is pending, suitable for presenting to the user
a string ID for the suite containing the test that is pending, intended to be unique across all suites in a run
an optional fully qualifed
Suite
class name containing the test that is pendingthe name of the test that is pending
the text of the test that is pending (may be the test name, or a suffix of the test name)
recorded events in the test.
an optional amount of time, in milliseconds, that was required to run the test that is pending
an optional
Formatter
that provides extra information that can be used by reporters in determining how to present this event to the userAn optional
Location
that provides information indicating where in the source code an event originated.an optional object that can be used to pass custom information to the reporter about the
TestPending
eventa name for the
Thread
about whose activity this event was reporteda
Long
indicating the time this event was reported, expressed in terms of the number of milliseconds since the standard base time known as "the epoch": January 1, 1970, 00:00:00 GMT