trait TestNGSuiteLike extends Suite
Implementation trait for class TestNGSuite
, which represents
a suite of tests that can be run with either TestNG or ScalaTest.
TestNGSuite
is a class, not a
trait, to minimize compile time given there is a slight compiler overhead to
mixing in traits compared to extending classes. If you need to mix the
behavior of TestNGSuite
into some other class, you can use this
trait instead, because class TestNGSuite
does nothing more than
extend this trait.
See the documentation of the class for a detailed
overview of TestNGSuite
.
- Self Type
- TestNGSuiteLike
- Source
- TestNGSuiteLike.scala
- Alphabetic
- By Inheritance
- TestNGSuiteLike
- Suite
- Serializable
- Serializable
- Assertions
- TripleEquals
- TripleEqualsSupport
- AnyRef
- Any
- Hide All
- Show All
- Public
- All
Type Members
-
class
AssertionsHelper
extends AnyRef
Helper class used by code generated by the
assert
macro.Helper class used by code generated by the
assert
macro.- Definition Classes
- Assertions
-
class
CheckingEqualizer[L] extends AnyRef
- Definition Classes
- TripleEqualsSupport
-
class
Equalizer[L] extends AnyRef
- Definition Classes
- TripleEqualsSupport
Value Members
-
final
def
!=(arg0: Any): Boolean
- Definition Classes
- AnyRef → Any
-
def
!==[T](right: Spread[T]): TripleEqualsInvocationOnSpread[T]
- Definition Classes
- TripleEqualsSupport
-
def
!==(right: Null): TripleEqualsInvocation[Null]
- Definition Classes
- TripleEqualsSupport
-
def
!==[T](right: T): TripleEqualsInvocation[T]
- Definition Classes
- TripleEqualsSupport
-
final
def
##(): Int
- Definition Classes
- AnyRef → Any
-
final
def
==(arg0: Any): Boolean
- Definition Classes
- AnyRef → Any
-
def
===[T](right: Spread[T]): TripleEqualsInvocationOnSpread[T]
- Definition Classes
- TripleEqualsSupport
-
def
===(right: Null): TripleEqualsInvocation[Null]
- Definition Classes
- TripleEqualsSupport
-
def
===[T](right: T): TripleEqualsInvocation[T]
- Definition Classes
- TripleEqualsSupport
-
final
def
asInstanceOf[T0]: T0
- Definition Classes
- Any
-
macro
def
assert(condition: Boolean, clue: Any)(implicit prettifier: Prettifier, pos: Position): Assertion
Assert that a boolean condition, described in
String
message
, is true.Assert that a boolean condition, described in
String
message
, is true. If the condition istrue
, this method returns normally. Else, it throwsTestFailedException
with a helpful error message appended with theString
obtained by invokingtoString
on the specifiedclue
as the exception's detail message.This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
- assert(a == b, "a good clue")
- assert(a != b, "a good clue")
- assert(a === b, "a good clue")
- assert(a !== b, "a good clue")
- assert(a > b, "a good clue")
- assert(a >= b, "a good clue")
- assert(a < b, "a good clue")
- assert(a <= b, "a good clue")
- assert(a startsWith "prefix", "a good clue")
- assert(a endsWith "postfix", "a good clue")
- assert(a contains "something", "a good clue")
- assert(a eq b, "a good clue")
- assert(a ne b, "a good clue")
- assert(a > 0 && b > 5, "a good clue")
- assert(a > 0 || b > 5, "a good clue")
- assert(a.isEmpty, "a good clue")
- assert(!a.isEmpty, "a good clue")
- assert(a.isInstanceOf[String], "a good clue")
- assert(a.length == 8, "a good clue")
- assert(a.size == 8, "a good clue")
- assert(a.exists(_ == 8), "a good clue")
At this time, any other form of expression will just get a
TestFailedException
with message saying the given expression was false. In the future, we will enhance this macro to give helpful error messages in more situations. In ScalaTest 2.0, however, this behavior was sufficient to allow the===
that returnsBoolean
to be the default in tests. This makes===
consistent between tests and production code.- condition
the boolean condition to assert
- clue
An objects whose
toString
method returns a message to include in a failure report.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifmessage
isnull
.TestFailedException
if the condition isfalse
.
-
macro
def
assert(condition: Boolean)(implicit prettifier: Prettifier, pos: Position): Assertion
Assert that a boolean condition is true.
Assert that a boolean condition is true. If the condition is
true
, this method returns normally. Else, it throwsTestFailedException
.This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
- assert(a == b)
- assert(a != b)
- assert(a === b)
- assert(a !== b)
- assert(a > b)
- assert(a >= b)
- assert(a < b)
- assert(a <= b)
- assert(a startsWith "prefix")
- assert(a endsWith "postfix")
- assert(a contains "something")
- assert(a eq b)
- assert(a ne b)
- assert(a > 0 && b > 5)
- assert(a > 0 || b > 5)
- assert(a.isEmpty)
- assert(!a.isEmpty)
- assert(a.isInstanceOf[String])
- assert(a.length == 8)
- assert(a.size == 8)
- assert(a.exists(_ == 8))
At this time, any other form of expression will get a
TestFailedException
with message saying the given expression was false. In the future, we will enhance this macro to give helpful error messages in more situations. In ScalaTest 2.0, however, this behavior was sufficient to allow the===
that returnsBoolean
to be the default in tests. This makes===
consistent between tests and production code.- condition
the boolean condition to assert
- Definition Classes
- Assertions
- Exceptions thrown
TestFailedException
if the condition isfalse
.
-
macro
def
assertCompiles(code: String)(implicit pos: Position): Assertion
Asserts that a given string snippet of code passes both the Scala parser and type checker.
Asserts that a given string snippet of code passes both the Scala parser and type checker.
You can use this to make sure a snippet of code compiles:
assertCompiles("val a: Int = 1")
Although
assertCompiles
is implemented with a macro that determines at compile time whether the snippet of code represented by the passed string compiles, errors (i.e., snippets of code that do not compile) are reported as test failures at runtime.- code
the snippet of code that should compile
- Definition Classes
- Assertions
-
macro
def
assertDoesNotCompile(code: String)(implicit pos: Position): Assertion
Asserts that a given string snippet of code does not pass either the Scala parser or type checker.
Asserts that a given string snippet of code does not pass either the Scala parser or type checker.
Often when creating libraries you may wish to ensure that certain arrangements of code that represent potential “user errors” do not compile, so that your library is more error resistant. ScalaTest's
Assertions
trait includes the following syntax for that purpose:assertDoesNotCompile("val a: String = \"a string")
Although
assertDoesNotCompile
is implemented with a macro that determines at compile time whether the snippet of code represented by the passed string doesn't compile, errors (i.e., snippets of code that do compile) are reported as test failures at runtime.Note that the difference between
assertTypeError
andassertDoesNotCompile
is thatassertDoesNotCompile
will succeed if the given code does not compile for any reason, whereasassertTypeError
will only succeed if the given code does not compile because of a type error. If the given code does not compile because of a syntax error, for example,assertDoesNotCompile
will return normally butassertTypeError
will throw aTestFailedException
.- code
the snippet of code that should not type check
- Definition Classes
- Assertions
-
def
assertResult(expected: Any)(actual: Any)(implicit prettifier: Prettifier, pos: Position): Assertion
Assert that the value passed as
expected
equals the value passed asactual
.Assert that the value passed as
expected
equals the value passed asactual
. If theactual
value equals theexpected
value (as determined by==
),assertResult
returns normally. Else,assertResult
throws aTestFailedException
whose detail message includes the expected and actual values.- expected
the expected value
- actual
the actual value, which should equal the passed
expected
value
- Definition Classes
- Assertions
- Exceptions thrown
TestFailedException
if the passedactual
value does not equal the passedexpected
value.
-
def
assertResult(expected: Any, clue: Any)(actual: Any)(implicit prettifier: Prettifier, pos: Position): Assertion
Assert that the value passed as
expected
equals the value passed asactual
.Assert that the value passed as
expected
equals the value passed asactual
. If theactual
equals theexpected
(as determined by==
),assertResult
returns normally. Else, ifactual
is not equal toexpected
,assertResult
throws aTestFailedException
whose detail message includes the expected and actual values, as well as theString
obtained by invokingtoString
on the passedclue
.- expected
the expected value
- clue
An object whose
toString
method returns a message to include in a failure report.- actual
the actual value, which should equal the passed
expected
value
- Definition Classes
- Assertions
- Exceptions thrown
TestFailedException
if the passedactual
value does not equal the passedexpected
value.
-
def
assertThrows[T <: AnyRef](f: ⇒ Any)(implicit classTag: ClassTag[T], pos: Position): Assertion
Ensure that an expected exception is thrown by the passed function value.
Ensure that an expected exception is thrown by the passed function value. The thrown exception must be an instance of the type specified by the type parameter of this method. This method invokes the passed function. If the function throws an exception that's an instance of the specified type, this method returns
Succeeded
. Else, whether the passed function returns normally or completes abruptly with a different exception, this method throwsTestFailedException
.Note that the type specified as this method's type parameter may represent any subtype of
AnyRef
, not justThrowable
or one of its subclasses. In Scala, exceptions can be caught based on traits they implement, so it may at times make sense to specify a trait that the intercepted exception's class must mix in. If a class instance is passed for a type that could not possibly be used to catch an exception (such asString
, for example), this method will complete abruptly with aTestFailedException
.Also note that the difference between this method and
intercept
is that this method does not return the expected exception, so it does not let you perform further assertions on that exception. Instead, this method returnsSucceeded
, which means it can serve as the last statement in an async- or safe-style suite. It also indicates to the reader of the code that nothing further is expected about the thrown exception other than its type. The recommended usage is to useassertThrows
by default,intercept
only when you need to inspect the caught exception further.- f
the function value that should throw the expected exception
- classTag
an implicit
ClassTag
representing the type of the specified type parameter.- returns
the
Succeeded
singleton, if an exception of the expected type is thrown
- Definition Classes
- Assertions
- Exceptions thrown
TestFailedException
if the passed function does not complete abruptly with an exception that's an instance of the specified type.
-
macro
def
assertTypeError(code: String)(implicit pos: Position): Assertion
Asserts that a given string snippet of code does not pass the Scala type checker, failing if the given snippet does not pass the Scala parser.
Asserts that a given string snippet of code does not pass the Scala type checker, failing if the given snippet does not pass the Scala parser.
Often when creating libraries you may wish to ensure that certain arrangements of code that represent potential “user errors” do not compile, so that your library is more error resistant. ScalaTest's
Assertions
trait includes the following syntax for that purpose:assertTypeError("val a: String = 1")
Although
assertTypeError
is implemented with a macro that determines at compile time whether the snippet of code represented by the passed string type checks, errors (i.e., snippets of code that do type check) are reported as test failures at runtime.Note that the difference between
assertTypeError
andassertDoesNotCompile
is thatassertDoesNotCompile
will succeed if the given code does not compile for any reason, whereasassertTypeError
will only succeed if the given code does not compile because of a type error. If the given code does not compile because of a syntax error, for example,assertDoesNotCompile
will return normally butassertTypeError
will throw aTestFailedException
.- code
the snippet of code that should not type check
- Definition Classes
- Assertions
-
val
assertionsHelper: AssertionsHelper
Helper instance used by code generated by macro assertion.
Helper instance used by code generated by macro assertion.
- Definition Classes
- Assertions
-
macro
def
assume(condition: Boolean, clue: Any)(implicit prettifier: Prettifier, pos: Position): Assertion
Assume that a boolean condition, described in
String
message
, is true.Assume that a boolean condition, described in
String
message
, is true. If the condition istrue
, this method returns normally. Else, it throwsTestCanceledException
with a helpful error message appended withString
obtained by invokingtoString
on the specifiedclue
as the exception's detail message.This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
- assume(a == b, "a good clue")
- assume(a != b, "a good clue")
- assume(a === b, "a good clue")
- assume(a !== b, "a good clue")
- assume(a > b, "a good clue")
- assume(a >= b, "a good clue")
- assume(a < b, "a good clue")
- assume(a <= b, "a good clue")
- assume(a startsWith "prefix", "a good clue")
- assume(a endsWith "postfix", "a good clue")
- assume(a contains "something", "a good clue")
- assume(a eq b, "a good clue")
- assume(a ne b, "a good clue")
- assume(a > 0 && b > 5, "a good clue")
- assume(a > 0 || b > 5, "a good clue")
- assume(a.isEmpty, "a good clue")
- assume(!a.isEmpty, "a good clue")
- assume(a.isInstanceOf[String], "a good clue")
- assume(a.length == 8, "a good clue")
- assume(a.size == 8, "a good clue")
- assume(a.exists(_ == 8), "a good clue")
At this time, any other form of expression will just get a
TestCanceledException
with message saying the given expression was false. In the future, we will enhance this macro to give helpful error messages in more situations. In ScalaTest 2.0, however, this behavior was sufficient to allow the===
that returnsBoolean
to be the default in tests. This makes===
consistent between tests and production code.- condition
the boolean condition to assume
- clue
An objects whose
toString
method returns a message to include in a failure report.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifmessage
isnull
.TestCanceledException
if the condition isfalse
.
-
macro
def
assume(condition: Boolean)(implicit prettifier: Prettifier, pos: Position): Assertion
Assume that a boolean condition is true.
Assume that a boolean condition is true. If the condition is
true
, this method returns normally. Else, it throwsTestCanceledException
.This method is implemented in terms of a Scala macro that will generate a more helpful error message for expressions of this form:
- assume(a == b)
- assume(a != b)
- assume(a === b)
- assume(a !== b)
- assume(a > b)
- assume(a >= b)
- assume(a < b)
- assume(a <= b)
- assume(a startsWith "prefix")
- assume(a endsWith "postfix")
- assume(a contains "something")
- assume(a eq b)
- assume(a ne b)
- assume(a > 0 && b > 5)
- assume(a > 0 || b > 5)
- assume(a.isEmpty)
- assume(!a.isEmpty)
- assume(a.isInstanceOf[String])
- assume(a.length == 8)
- assume(a.size == 8)
- assume(a.exists(_ == 8))
At this time, any other form of expression will just get a
TestCanceledException
with message saying the given expression was false. In the future, we will enhance this macro to give helpful error messages in more situations. In ScalaTest 2.0, however, this behavior was sufficient to allow the===
that returnsBoolean
to be the default in tests. This makes===
consistent between tests and production code.- condition
the boolean condition to assume
- Definition Classes
- Assertions
- Exceptions thrown
TestCanceledException
if the condition isfalse
.
-
def
cancel(cause: Throwable)(implicit pos: Position): Nothing
Throws
TestCanceledException
, with the passedThrowable
cause, to indicate a test failed.Throws
TestCanceledException
, with the passedThrowable
cause, to indicate a test failed. ThegetMessage
method of the thrownTestCanceledException
will returncause.toString
.- cause
a
Throwable
that indicates the cause of the cancellation.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifcause
isnull
-
def
cancel(message: String, cause: Throwable)(implicit pos: Position): Nothing
Throws
TestCanceledException
, with the passedString
message
as the exception's detail message andThrowable
cause, to indicate a test failed.Throws
TestCanceledException
, with the passedString
message
as the exception's detail message andThrowable
cause, to indicate a test failed.- message
A message describing the failure.
- cause
A
Throwable
that indicates the cause of the failure.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifmessage
orcause
isnull
-
def
cancel(message: String)(implicit pos: Position): Nothing
Throws
TestCanceledException
, with the passedString
message
as the exception's detail message, to indicate a test was canceled.Throws
TestCanceledException
, with the passedString
message
as the exception's detail message, to indicate a test was canceled.- message
A message describing the cancellation.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifmessage
isnull
-
def
cancel()(implicit pos: Position): Nothing
Throws
TestCanceledException
to indicate a test was canceled.Throws
TestCanceledException
to indicate a test was canceled.- Definition Classes
- Assertions
-
def
clone(): AnyRef
- Attributes
- protected[java.lang]
- Definition Classes
- AnyRef
- Annotations
- @throws( ... )
-
def
conversionCheckedConstraint[A, B](implicit equivalenceOfA: Equivalence[A], cnv: (B) ⇒ A): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
def
convertEquivalenceToAToBConstraint[A, B](equivalenceOfB: Equivalence[B])(implicit ev: <:<[A, B]): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
def
convertEquivalenceToAToBConversionConstraint[A, B](equivalenceOfB: Equivalence[B])(implicit ev: (A) ⇒ B): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
def
convertEquivalenceToBToAConstraint[A, B](equivalenceOfA: Equivalence[A])(implicit ev: <:<[B, A]): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
def
convertEquivalenceToBToAConversionConstraint[A, B](equivalenceOfA: Equivalence[A])(implicit ev: (B) ⇒ A): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
def
convertToCheckingEqualizer[T](left: T): CheckingEqualizer[T]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
implicit
def
convertToEqualizer[T](left: T): Equalizer[T]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
def
defaultEquality[A]: Equality[A]
- Definition Classes
- TripleEqualsSupport
-
final
def
eq(arg0: AnyRef): Boolean
- Definition Classes
- AnyRef
-
def
equals(arg0: Any): Boolean
- Definition Classes
- AnyRef → Any
-
final
def
execute(testName: String = null, configMap: ConfigMap = ConfigMap.empty, color: Boolean = true, durations: Boolean = false, shortstacks: Boolean = false, fullstacks: Boolean = false, stats: Boolean = false): Unit
Executes one or more tests in this
Suite
, printing results to the standard output.Executes one or more tests in this
Suite
, printing results to the standard output.This method invokes
run
on itself, passing in values that can be configured via the parameters to this method, all of which have default values. This behavior is convenient when working with ScalaTest in the Scala interpreter. Here's a summary of this method's parameters and how you can use them:The
testName
parameterIf you leave
testName
at its default value (ofnull
), this method will passNone
to thetestName
parameter ofrun
, and as a result all the tests in this suite will be executed. If you specify atestName
, this method will passSome(testName)
torun
, and only that test will be run. Thus to run all tests in a suite from the Scala interpreter, you can write:scala> (new ExampleSuite).execute()
(The above syntax actually invokes the overloaded parameterless form of
execute
, which calls this form with its default parameter values.) To run just the test named"my favorite test"
in a suite from the Scala interpreter, you would write:scala> (new ExampleSuite).execute("my favorite test")
Or:
scala> (new ExampleSuite).execute(testName = "my favorite test")
The
configMap
parameterIf you provide a value for the
configMap
parameter, this method will pass it torun
. If not, the default value of an emptyMap
will be passed. For more information on how to use a config map to configure your test suites, see the config map section in the main documentation for this trait. Here's an example in which you configure a run with the name of an input file:scala> (new ExampleSuite).execute(configMap = Map("inputFileName" -> "in.txt")
The
color
parameterIf you leave the
color
parameter unspecified, this method will configure the reporter it passes torun
to print to the standard output in color (via ansi escape characters). If you don't want color output, specify false forcolor
, like this:scala> (new ExampleSuite).execute(color = false)
The
durations
parameterIf you leave the
durations
parameter unspecified, this method will configure the reporter it passes torun
to not print durations for tests and suites to the standard output. If you want durations printed, specify true fordurations
, like this:scala> (new ExampleSuite).execute(durations = true)
The
shortstacks
andfullstacks
parametersIf you leave both the
shortstacks
andfullstacks
parameters unspecified, this method will configure the reporter it passes torun
to not print stack traces for failed tests if it has a stack depth that identifies the offending line of test code. If you prefer a short stack trace (10 to 15 stack frames) to be printed with any test failure, specify true forshortstacks
:scala> (new ExampleSuite).execute(shortstacks = true)
For full stack traces, set
fullstacks
to true:scala> (new ExampleSuite).execute(fullstacks = true)
If you specify true for both
shortstacks
andfullstacks
, you'll get full stack traces.The
stats
parameterIf you leave the
stats
parameter unspecified, this method will not fireRunStarting
and eitherRunCompleted
orRunAborted
events to the reporter it passes torun
. If you specify true forstats
, this method will fire the run events to the reporter, and the reporter will print the expected test count before the run, and various statistics after, including the number of suites completed and number of tests that succeeded, failed, were ignored or marked pending. Here's how you get the stats:scala> (new ExampleSuite).execute(stats = true)
To summarize, this method will pass to
run
:testName
-None
if this method'stestName
parameter is left at its default value ofnull
, elseSome(testName)
.reporter
- a reporter that prints to the standard outputstopper
- aStopper
whoseapply
method always returnsfalse
filter
- aFilter
constructed withNone
fortagsToInclude
andSet()
fortagsToExclude
configMap
- theconfigMap
passed to this methoddistributor
-None
tracker
- a newTracker
Note: In ScalaTest, the terms "execute" and "run" basically mean the same thing and can be used interchangably. The reason this method isn't named
run
is that it takes advantage of default arguments, and you can't mix overloaded methods and default arguments in Scala. (If namedrun
, this method would have the same name but different arguments than the mainrun
method that takes seven arguments. Thus it would overload and couldn't be used with default argument values.)Design note: This method has two "features" that may seem unidiomatic. First, the default value of
testName
isnull
. Normally in Scala the type oftestName
would beOption[String]
and the default value would beNone
, as it is in this trait'srun
method. Thenull
value is used here for two reasons. First, in ScalaTest 1.5,execute
was changed from four overloaded methods to one method with default values, taking advantage of the default and named parameters feature introduced in Scala 2.8. To not break existing source code,testName
needed to have typeString
, as it did in two of the overloadedexecute
methods prior to 1.5. The other reason is thatexecute
has always been designed to be called primarily from an interpeter environment, such as the Scala REPL (Read-Evaluate-Print-Loop). In an interpreter environment, minimizing keystrokes is king. AString
type with anull
default value lets users typesuite.execute("my test name")
rather thansuite.execute(Some("my test name"))
, saving several keystrokes.The second non-idiomatic feature is that
shortstacks
andfullstacks
are all lower case rather than camel case. This is done to be consistent with theShell
, which also uses those forms. The reason lower case is used in theShell
is to save keystrokes in an interpreter environment. Most Unix commands, for example, are all lower case, making them easier and quicker to type. In the ScalaTestShell
, methods likeshortstacks
,fullstacks
, andnostats
, etc., are designed to be all lower case so they feel more like shell commands than methods.- testName
the name of one test to run.
- configMap
a
Map
of key-value pairs that can be used by the executingSuite
of tests.- color
a boolean that configures whether output is printed in color
- durations
a boolean that configures whether test and suite durations are printed to the standard output
- shortstacks
a boolean that configures whether short stack traces should be printed for test failures
- fullstacks
a boolean that configures whether full stack traces should be printed for test failures
- stats
a boolean that configures whether test and suite statistics are printed to the standard output
- Definition Classes
- Suite
- Exceptions thrown
IllegalArgumentException
iftestName
is defined, but no test with the specified test name exists in thisSuite
NullArgumentException
if the passedconfigMap
parameter isnull
.
-
def
expectedTestCount(filter: Filter): Int
The total number of tests that are expected to run when this
Suite
'srun
method is invoked.The total number of tests that are expected to run when this
Suite
'srun
method is invoked.This trait's implementation of this method returns the sum of:
- the size of the
testNames
List
, minus the number of tests marked as ignored and any tests that are exluded by the passedFilter
- the sum of the values obtained by invoking
expectedTestCount
on every nestedSuite
contained innestedSuites
- filter
a
Filter
with which to filter tests to count based on their tags
- Definition Classes
- Suite
- the size of the
-
def
fail(cause: Throwable)(implicit pos: Position): Nothing
Throws
TestFailedException
, with the passedThrowable
cause, to indicate a test failed.Throws
TestFailedException
, with the passedThrowable
cause, to indicate a test failed. ThegetMessage
method of the thrownTestFailedException
will returncause.toString
.- cause
a
Throwable
that indicates the cause of the failure.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifcause
isnull
-
def
fail(message: String, cause: Throwable)(implicit pos: Position): Nothing
Throws
TestFailedException
, with the passedString
message
as the exception's detail message andThrowable
cause, to indicate a test failed.Throws
TestFailedException
, with the passedString
message
as the exception's detail message andThrowable
cause, to indicate a test failed.- message
A message describing the failure.
- cause
A
Throwable
that indicates the cause of the failure.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifmessage
orcause
isnull
-
def
fail(message: String)(implicit pos: Position): Nothing
Throws
TestFailedException
, with the passedString
message
as the exception's detail message, to indicate a test failed.Throws
TestFailedException
, with the passedString
message
as the exception's detail message, to indicate a test failed.- message
A message describing the failure.
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
ifmessage
isnull
-
def
fail()(implicit pos: Position): Nothing
Throws
TestFailedException
to indicate a test failed.Throws
TestFailedException
to indicate a test failed.- Definition Classes
- Assertions
-
def
finalize(): Unit
- Attributes
- protected[java.lang]
- Definition Classes
- AnyRef
- Annotations
- @throws( classOf[java.lang.Throwable] )
-
final
def
getClass(): Class[_]
- Definition Classes
- AnyRef → Any
-
def
hashCode(): Int
- Definition Classes
- AnyRef → Any
-
def
intercept[T <: AnyRef](f: ⇒ Any)(implicit classTag: ClassTag[T], pos: Position): T
Intercept and return an exception that's expected to be thrown by the passed function value.
Intercept and return an exception that's expected to be thrown by the passed function value. The thrown exception must be an instance of the type specified by the type parameter of this method. This method invokes the passed function. If the function throws an exception that's an instance of the specified type, this method returns that exception. Else, whether the passed function returns normally or completes abruptly with a different exception, this method throws
TestFailedException
.Note that the type specified as this method's type parameter may represent any subtype of
AnyRef
, not justThrowable
or one of its subclasses. In Scala, exceptions can be caught based on traits they implement, so it may at times make sense to specify a trait that the intercepted exception's class must mix in. If a class instance is passed for a type that could not possibly be used to catch an exception (such asString
, for example), this method will complete abruptly with aTestFailedException
.Also note that the difference between this method and
assertThrows
is that this method returns the expected exception, so it lets you perform further assertions on that exception. By contrast, theassertThrows
method returnsSucceeded
, which means it can serve as the last statement in an async- or safe-style suite.assertThrows
also indicates to the reader of the code that nothing further is expected about the thrown exception other than its type. The recommended usage is to useassertThrows
by default,intercept
only when you need to inspect the caught exception further.- f
the function value that should throw the expected exception
- classTag
an implicit
ClassTag
representing the type of the specified type parameter.- returns
the intercepted exception, if it is of the expected type
- Definition Classes
- Assertions
- Exceptions thrown
TestFailedException
if the passed function does not complete abruptly with an exception that's an instance of the specified type.
-
final
def
isInstanceOf[T0]: Boolean
- Definition Classes
- Any
-
def
lowPriorityConversionCheckedConstraint[A, B](implicit equivalenceOfB: Equivalence[B], cnv: (A) ⇒ B): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
def
lowPriorityTypeCheckedConstraint[A, B](implicit equivalenceOfB: Equivalence[B], ev: <:<[A, B]): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
final
def
ne(arg0: AnyRef): Boolean
- Definition Classes
- AnyRef
-
def
nestedSuites: IndexedSeq[Suite]
An immutable
IndexedSeq
of thisSuite
object's nestedSuite
s.An immutable
IndexedSeq
of thisSuite
object's nestedSuite
s. If thisSuite
contains no nestedSuite
s, this method returns an emptyIndexedSeq
. This trait's implementation of this method returns an emptyList
.- Definition Classes
- Suite
-
final
def
notify(): Unit
- Definition Classes
- AnyRef
-
final
def
notifyAll(): Unit
- Definition Classes
- AnyRef
-
def
pending: Assertion with PendingStatement
Throws
TestPendingException
to indicate a test is pending.Throws
TestPendingException
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 it is intended to test, has not yet been implemented.Note: This method always completes abruptly with a
TestPendingException
. Thus it always has a side effect. Methods with side effects are usually invoked with parentheses, as inpending()
. This method is defined as a parameterless method, in flagrant contradiction to recommended Scala style, because it forms a kind of DSL for pending tests. It enables tests in suites such asFunSuite
orFunSpec
to be denoted by placing "(pending)
" after the test name, as in:test("that style rules are not laws") (pending)
Readers of the code see "pending" in parentheses, which looks like a little note attached to the test name to indicate it is pending. Whereas "
(pending())
looks more like a method call, "(pending)
" lets readers stay at a higher level, forgetting how it is implemented and just focusing on the intent of the programmer who wrote the code.- Definition Classes
- Assertions
-
def
pendingUntilFixed(f: ⇒ Unit)(implicit pos: Position): Assertion with PendingStatement
Execute the passed block of code, and if it completes abruptly, throw
TestPendingException
, else throwTestFailedException
.Execute the passed block of code, and if it completes abruptly, throw
TestPendingException
, else throwTestFailedException
.This method can be used to temporarily change a failing test into a pending test in such a way that it will automatically turn back into a failing test once the problem originally causing the test to fail has been fixed. At that point, you need only remove the
pendingUntilFixed
call. In other words, apendingUntilFixed
surrounding a block of code that isn't broken is treated as a test failure. The motivation for this behavior is to encourage people to removependingUntilFixed
calls when there are no longer needed.This method facilitates a style of testing in which tests are written before the code they test. Sometimes you may encounter a test failure that requires more functionality than you want to tackle without writing more tests. In this case you can mark the bit of test code causing the failure with
pendingUntilFixed
. You can then write more tests and functionality that eventually will get your production code to a point where the original test won't fail anymore. At this point the code block marked withpendingUntilFixed
will no longer throw an exception (because the problem has been fixed). This will in turn causependingUntilFixed
to throwTestFailedException
with a detail message explaining you need to go back and remove thependingUntilFixed
call as the problem orginally causing your test code to fail has been fixed.- f
a block of code, which if it completes abruptly, should trigger a
TestPendingException
- Definition Classes
- Assertions
- Exceptions thrown
TestPendingException
if the passed block of code completes abruptly with anException
orAssertionError
-
def
rerunner: Option[String]
The fully qualified class name of the rerunner to rerun this suite.
The fully qualified class name of the rerunner to rerun this suite. This implementation will look at this.getClass and see if it is either an accessible Suite, or it has a WrapWith annotation. If so, it returns the fully qualified class name wrapped in a Some, or else it returns None.
- Definition Classes
- Suite
-
def
run(testName: Option[String], args: Args): Status
Execute this
TestNGSuite
.Execute this
TestNGSuite
.- testName
an optional name of one test to execute. If
None
, this class will execute all relevant tests. I.e.,None
acts like a wildcard that means execute all relevant tests in thisTestNGSuite
.- args
the
Args
for this run- returns
a
Status
object that indicates when all tests and nested suites started by this method have completed, and whether or not a failure occurred.
- Definition Classes
- TestNGSuiteLike → Suite
-
final
def
runNestedSuites(args: Args): Status
Throws
UnsupportedOperationException
, because this method is unused by this trait, given this trait'srun
method delegates to TestNG to run its tests.Throws
UnsupportedOperationException
, because this method is unused by this trait, given this trait'srun
method delegates to TestNG to run its tests.The main purpose of this method implementation is to render a compiler error an attempt to mix in a trait that overrides
runNestedSuites
. Because this trait does not actually userunNestedSuites
, the attempt to mix in behavior would very likely not work.- args
the
Args
for this run- returns
a
Status
object that indicates when all nested suites started by this method have completed, and whether or not a failure occurred.
- Attributes
- protected
- Definition Classes
- TestNGSuiteLike → Suite
- Exceptions thrown
UnsupportedOperationException
always.
-
final
def
runTest(testName: String, args: Args): Status
Throws
UnsupportedOperationException
, because this method is unused by this trait, given this trait'srun
method delegates to TestNG to run its tests.Throws
UnsupportedOperationException
, because this method is unused by this trait, given this trait'srun
method delegates to TestNG to run its tests.The main purpose of this method implementation is to render a compiler error an attempt to mix in a trait that overrides
runTest
. Because this trait does not actually userunTest
, the attempt to mix in behavior would very likely not work.- testName
the name of one test to run.
- args
the
Args
for this run- returns
a
Status
object that indicates when the test started by this method has completed, and whether or not it failed .
- Attributes
- protected
- Definition Classes
- TestNGSuiteLike → Suite
- Exceptions thrown
UnsupportedOperationException
always.
-
final
def
runTests(testName: Option[String], args: Args): Status
Throws
UnsupportedOperationException
, because this method is unused by this trait, given this trait'srun
method delegates to TestNG to run its tests.Throws
UnsupportedOperationException
, because this method is unused by this trait, given this trait'srun
method delegates to TestNG to run its tests.The main purpose of this method implementation is to render a compiler error an attempt to mix in a trait that overrides
runTests
. Because this trait does not actually userunTests
, the attempt to mix in behavior would very likely not work.- testName
an optional name of one test to run. If
None
, all relevant tests should be run. I.e.,None
acts like a wildcard that means run all relevant tests in thisSuite
.- args
the
Args
for this run- returns
a
Status
object that indicates when all tests started by this method have completed, and whether or not a failure occurred.
- Attributes
- protected
- Definition Classes
- TestNGSuiteLike → Suite
- Exceptions thrown
UnsupportedOperationException
always.
-
final
val
styleName: String
Suite style name.
Suite style name.
- Definition Classes
- TestNGSuiteLike → Suite
-
final
val
succeed: Assertion
The
Succeeded
singleton.The
Succeeded
singleton.You can use
succeed
to solve a type error when an async test does not end in eitherFuture[Assertion]
orAssertion
. BecauseAssertion
is a type alias forSucceeded.type
, puttingsucceed
at the end of a test body (or at the end of a function being used to map the final future of a test body) will solve the type error.- Definition Classes
- Assertions
-
def
suiteId: String
A string ID for this
Suite
that is intended to be unique among all suites reported during a run.A string ID for this
Suite
that is intended to be unique among all suites reported during a run.This trait's implementation of this method returns the fully qualified name of this object's class. Each suite reported during a run will commonly be an instance of a different
Suite
class, and in such cases, this default implementation of this method will suffice. However, in special cases you may need to override this method to ensure it is unique for each reported suite. For example, if you write aSuite
subclass that reads in a file whose name is passed to its constructor and dynamically creates a suite of tests based on the information in that file, you will likely need to override this method in yourSuite
subclass, perhaps by appending the pathname of the file to the fully qualified class name. That way if you run a suite of tests based on a directory full of these files, you'll have unique suite IDs for each reported suite.The suite ID is intended to be unique, because ScalaTest does not enforce that it is unique. If it is not unique, then you may not be able to uniquely identify a particular test of a particular suite. This ability is used, for example, to dynamically tag tests as having failed in the previous run when rerunning only failed tests.
- returns
this
Suite
object's ID.
- Definition Classes
- Suite
-
def
suiteName: String
A user-friendly suite name for this
Suite
.A user-friendly suite name for this
Suite
.This trait's implementation of this method returns the simple name of this object's class. This trait's implementation of
runNestedSuites
calls this method to obtain a name forReport
s to pass to thesuiteStarting
,suiteCompleted
, andsuiteAborted
methods of theReporter
.- returns
this
Suite
object's suite name.
- Definition Classes
- Suite
-
final
def
synchronized[T0](arg0: ⇒ T0): T0
- Definition Classes
- AnyRef
-
def
tags: Map[String, Set[String]]
A
Map
whose keys areString
names of tests that are tagged and whose associated values are theSet
of tag names for the test.A
Map
whose keys areString
names of tests that are tagged and whose associated values are theSet
of tag names for the test. If a test has no associated tags, its name does not appear as a key in the returnedMap
. If thisSuite
contains no tests with tags, this method returns an emptyMap
.This trait's implementation of this method uses Java reflection to discover any Java annotations attached to its test methods. The fully qualified name of each unique annotation that extends
TagAnnotation
is considered a tag. This trait's implementation of this method, therefore, places one key/value pair into to theMap
for each test for which a tag annotation is discovered through reflection.In addition to test methods annotations, this trait's implementation will also auto-tag test methods with class level annotations. For example, if you annotate @Ignore at the class level, all test methods in the class will be auto-annotated with @Ignore.
Subclasses may override this method to define and/or discover tags in a custom manner, but overriding method implementations should never return an empty
Set
as a value. If a test has no tags, its name should not appear as a key in the returnedMap
.- Definition Classes
- TestNGSuiteLike → Suite
-
def
testDataFor(testName: String, theConfigMap: ConfigMap = ConfigMap.empty): TestData
Provides a
TestData
instance for the passed test name, given the passed config map.Provides a
TestData
instance for the passed test name, given the passed config map.This method is used to obtain a
TestData
instance to pass towithFixture(NoArgTest)
andwithFixture(OneArgTest)
and thebeforeEach
andafterEach
methods of traitBeforeAndAfterEach
.- testName
the name of the test for which to return a
TestData
instance- theConfigMap
the config map to include in the returned
TestData
- returns
a
TestData
instance for the specified test, which includes the specified config map
- Definition Classes
- TestNGSuiteLike → Suite
-
def
testNames: Set[String]
A
Set
of test names.A
Set
of test names. If thisSuite
contains no tests, this method returns an emptySet
.This trait's implementation of this method returns an empty
Set
.- Definition Classes
- TestNGSuiteLike → Suite
-
def
toString(): String
- Definition Classes
- AnyRef → Any
-
def
typeCheckedConstraint[A, B](implicit equivalenceOfA: Equivalence[A], ev: <:<[B, A]): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
implicit
def
unconstrainedEquality[A, B](implicit equalityOfA: Equality[A]): CanEqual[A, B]
- Definition Classes
- TripleEquals → TripleEqualsSupport
-
final
def
wait(): Unit
- Definition Classes
- AnyRef
- Annotations
- @throws( ... )
-
final
def
wait(arg0: Long, arg1: Int): Unit
- Definition Classes
- AnyRef
- Annotations
- @throws( ... )
-
final
def
wait(arg0: Long): Unit
- Definition Classes
- AnyRef
- Annotations
- @throws( ... )
-
def
withClue[T](clue: Any)(fun: ⇒ T): T
Executes the block of code passed as the second parameter, and, if it completes abruptly with a
ModifiableMessage
exception, prepends the "clue" string passed as the first parameter to the beginning of the detail message of that thrown exception, then rethrows it.Executes the block of code passed as the second parameter, and, if it completes abruptly with a
ModifiableMessage
exception, prepends the "clue" string passed as the first parameter to the beginning of the detail message of that thrown exception, then rethrows it. If clue does not end in a white space character, one space will be added between it and the existing detail message (unless the detail message is not defined).This method allows you to add more information about what went wrong that will be reported when a test fails. Here's an example:
withClue("(Employee's name was: " + employee.name + ")") { intercept[IllegalArgumentException] { employee.getTask(-1) } }
If an invocation of
intercept
completed abruptly with an exception, the resulting message would be something like:(Employee's name was Bob Jones) Expected IllegalArgumentException to be thrown, but no exception was thrown
- Definition Classes
- Assertions
- Exceptions thrown
NullArgumentException
if the passedclue
isnull
Deprecated Value Members
-
final
def
execute: Unit
The parameterless
execute
method has been deprecated and will be removed in a future version of ScalaTest. Please invokeexecute
with empty parens instead:execute()
.The parameterless
execute
method has been deprecated and will be removed in a future version of ScalaTest. Please invokeexecute
with empty parens instead:execute()
.The original purpose of this method, which simply invokes the other overloaded form of
execute
with default parameter values, was to serve as a mini-DSL for the Scala interpreter. It allowed you to execute aSuite
in the interpreter with a minimum of finger typing:scala> org.scalatest.run(new SetSpec) An empty Set - should have size 0 - should produce NoSuchElementException when head is invoked !!! IGNORED !!!
However it uses postfix notation, which is now behind a language feature import. Thus better to use the other
execute
method ororg.scalatest.run
:(new ExampleSuite).execute() // or org.scalatest.run(new ExampleSuite)
- Definition Classes
- Suite
- Annotations
- @deprecated
- Deprecated
The parameterless execute method has been deprecated and will be removed in a future version of ScalaTest. Please invoke execute with empty parens instead: execute().
-
def
trap[T](f: ⇒ T): Throwable
Trap and return any thrown exception that would normally cause a ScalaTest test to fail, or create and return a new
RuntimeException
indicating no exception is thrown.Trap and return any thrown exception that would normally cause a ScalaTest test to fail, or create and return a new
RuntimeException
indicating no exception is thrown.This method is intended to be used in the Scala interpreter to eliminate large stack traces when trying out ScalaTest assertions and matcher expressions. It is not intended to be used in regular test code. If you want to ensure that a bit of code throws an expected exception, use
intercept
, nottrap
. Here's an example interpreter session withouttrap
:scala> import org.scalatest._ import org.scalatest._ scala> import Matchers._ import Matchers._ scala> val x = 12 a: Int = 12 scala> x shouldEqual 13 org.scalatest.exceptions.TestFailedException: 12 did not equal 13 at org.scalatest.Assertions$class.newAssertionFailedException(Assertions.scala:449) at org.scalatest.Assertions$.newAssertionFailedException(Assertions.scala:1203) at org.scalatest.Assertions$AssertionsHelper.macroAssertTrue(Assertions.scala:417) at .<init>(<console>:15) at .<clinit>(<console>) at .<init>(<console>:7) at .<clinit>(<console>) at $print(<console>) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at scala.tools.nsc.interpreter.IMain$ReadEvalPrint.call(IMain.scala:731) at scala.tools.nsc.interpreter.IMain$Request.loadAndRun(IMain.scala:980) at scala.tools.nsc.interpreter.IMain.loadAndRunReq$1(IMain.scala:570) at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:601) at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:565) at scala.tools.nsc.interpreter.ILoop.reallyInterpret$1(ILoop.scala:745) at scala.tools.nsc.interpreter.ILoop.interpretStartingWith(ILoop.scala:790) at scala.tools.nsc.interpreter.ILoop.command(ILoop.scala:702) at scala.tools.nsc.interpreter.ILoop.processLine$1(ILoop.scala:566) at scala.tools.nsc.interpreter.ILoop.innerLoop$1(ILoop.scala:573) at scala.tools.nsc.interpreter.ILoop.loop(ILoop.scala:576) at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply$mcZ$sp(ILoop.scala:867) at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply(ILoop.scala:822) at scala.tools.nsc.interpreter.ILoop$$anonfun$process$1.apply(ILoop.scala:822) at scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135) at scala.tools.nsc.interpreter.ILoop.process(ILoop.scala:822) at scala.tools.nsc.MainGenericRunner.runTarget$1(MainGenericRunner.scala:83) at scala.tools.nsc.MainGenericRunner.process(MainGenericRunner.scala:96) at scala.tools.nsc.MainGenericRunner$.main(MainGenericRunner.scala:105) at scala.tools.nsc.MainGenericRunner.main(MainGenericRunner.scala)
That's a pretty tall stack trace. Here's what it looks like when you use
trap
:scala> trap { x shouldEqual 13 } res1: Throwable = org.scalatest.exceptions.TestFailedException: 12 did not equal 13
Much less clutter. Bear in mind, however, that if no exception is thrown by the passed block of code, the
trap
method will create a newNormalResult
(a subclass ofThrowable
made for this purpose only) and return that. If the result was theUnit
value, it will simply say that no exception was thrown:scala> trap { x shouldEqual 12 } res2: Throwable = No exception was thrown.
If the passed block of code results in a value other than
Unit
, theNormalResult
'stoString
will print the value:scala> trap { "Dude!" } res3: Throwable = No exception was thrown. Instead, result was: "Dude!"
Although you can access the result value from the
NormalResult
, its type isAny
and therefore not very convenient to use. It is not intended thattrap
be used in test code. The sole intended use case fortrap
is decluttering Scala interpreter sessions by eliminating stack traces when executing assertion and matcher expressions.- Definition Classes
- Assertions
- Annotations
- @deprecated
- Deprecated
The trap method is no longer needed for demos in the REPL, which now abreviates stack traces, and will be removed in a future version of ScalaTest