The total number of tests that are expected to run when this Suite
's run
method is invoked.
The total number of tests that are expected to run when this Suite
's run
method is invoked.
a Filter
with which to filter tests to count based on their tags
An immutable IndexedSeq
of this SuiteMixin
object's nested Suite
s.
An immutable IndexedSeq
of this SuiteMixin
object's nested Suite
s. If this SuiteMixin
contains no nested Suite
s,
this method returns an empty IndexedSeq
.
The fully qualified name of the class that can be used to rerun this suite.
The fully qualified name of the class that can be used to rerun this suite.
Runs this suite of tests.
Runs this suite of tests.
an optional name of one test to execute. If None
, all relevant tests should be executed.
I.e., None
acts like a wildcard that means execute all relevant tests in this Suite
.
the Args
for this run
a Status
object that indicates when all tests and nested suites started by this method have completed, and whether or not a failure occurred.
Runs zero to many of this suite's nested suites.
Runs zero to many of this suite's nested suites.
the Args
for this run
a Status
object that indicates when all nested suites started by this method have completed, and whether or not a failure occurred.
Runs zero to many of this suite's tests.
Runs zero to many of this suite's tests.
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 this Suite
.
the Args
for this run
a Status
object that indicates when all tests started by this method have completed, and whether or not a failure occurred.
This suite's style name.
This suite's style name.
This lifecycle method provides a string that is used to determine whether this suite object's style is one of the chosen styles for the project.
A Map
whose keys are String
tag names with which tests in this Suite
are marked, and
whose values are the Set
of test names marked with each tag.
A Map
whose keys are String
tag names with which tests in this Suite
are marked, and
whose values are the Set
of test names marked with each tag. If this Suite
contains no tags, this
method returns an empty Map
.
Subclasses may implement 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 tag has no tests, its name should not appear as a key in the
returned Map
.
A Set
of test names.
A Set
of test names. If this Suite
contains no tests, this method returns an empty Set
.
Although subclass and subtrait implementations of this method may return a Set
whose iterator produces String
test names in a well-defined order, the contract of this method does not required a defined order. Subclasses are free to
implement this method and return test names in either a defined or undefined order.
Runs the passed test function with a fixture established by this method.
Runs the passed test function with a fixture established by this method.
This method should set up the fixture needed by the tests of the
current suite, invoke the test function, and if needed, perform any clean
up needed after the test completes. Because the NoArgTest
function
passed to this method takes no parameters, preparing the fixture will require
side effects, such as initializing an external database.
the no-arg test function to run with a fixture
Defines a method (that takes a TestData
) to be run after
each of this suite's tests.
Defines a method (that takes a TestData
) to be run after
each of this suite's tests.
This trait's implementation
of runTest
invokes this method after running
each test (passing in a TestData
containing the configMap
passed
to it), thus this method can be used to tear down a test fixture
needed by each test. This trait's implementation of this method invokes the
overloaded form of afterEach
that takes configMap
.
After the deprecation cycle, this method will invoke the no-arg form of afterEach
.
Defines a method to be run after each of this suite's tests.
Defines a method to be run after each of this suite's tests.
This trait's implementation
of runTest
invokes the overloaded form of this method that
takes a configMap
map after running
each test. This trait's implementation of that afterEach(Map[String, Any])
method simply invokes this
afterEach()
method. Thus this method can be used to tear down a test fixture
needed by each test, when you don't need anything from the configMap
.
This trait's implementation of this method does nothing.
Defines a method (that takes a TestData
) to be run before
each of this suite's tests.
Defines a method (that takes a TestData
) to be run before
each of this suite's tests.
This trait's implementation
of runTest
invokes this method before running
each test (passing in the configMap
passed to it), thus this
method can be used to set up a test fixture
needed by each test. This trait's implementation of this method invokes the
overloaded form of beforeEach
that takes configMap
.
After the deprecation cycle, this method will invoke the no-arg form of beforeEach
.
Defines a method to be run before each of this suite's tests.
Defines a method to be run before each of this suite's tests.
This trait's implementation
of runTest
invokes the overloaded form of this method that
takes a configMap
before running
each test. This trait's implementation of that beforeEach(Map[String, Any])
method simply invokes this
beforeEach()
method. Thus this method can be used to set up a test fixture
needed by each test, when you don't need anything from the configMap
.
This trait's implementation of this method does nothing.
Run a test surrounded by calls to beforeEach
and afterEach
.
Run a test surrounded by calls to beforeEach
and afterEach
.
This trait's implementation of this method ("this method") invokes
beforeEach(configMap)
before running each test and afterEach(configMap)
after running each test. It runs each test by invoking super.runTest
, passing along
the two parameters passed to it.
If any invocation of beforeEach
completes abruptly with an exception, this
method will complete abruptly with the same exception. If any call to
super.runTest
completes abruptly with an exception, this method
will complete abruptly with the same exception, however, before doing so, it will
invoke afterEach
. If <cod>afterEach also completes abruptly with an exception, this
method will nevertheless complete abruptly with the exception previously thrown by super.runTest
.
If super.runTest
returns normally, but afterEach
completes abruptly with an
exception, this method will complete abruptly with the exception thrown by afterEach
.
the name of one test to run.
the Args
for this run
a Status
object that indicates when the test started by this method has completed, and whether or not it failed .
This overloaded form of afterEach
has been deprecated and will
be removed in a future version of ScalaTest. Please use afterEach(TestData)
instead.
This overloaded form of afterEach
has been deprecated and will
be removed in a future version of ScalaTest. Please use afterEach(TestData)
instead.
During the deprecation cycle, this trait's implementation
of afterEach(TestData)
invokes will this method.
This trait's implementation of this method invokes the
overloaded form of afterEach
that takes no configMap
.
Please use afterEach(TestData) instead.
This overloaded form of beforeEach
has been deprecated and will
be removed in a future version of ScalaTest. Please use beforeEach(TestData)
instead.
This overloaded form of beforeEach
has been deprecated and will
be removed in a future version of ScalaTest. Please use beforeEach(TestData)
instead.
During the deprecation cycle, this trait's implementation
of beforeEach(TestData)
invokes will this method.
This trait's implementation of this method invokes the
overloaded form of beforeEach
that takes no configMap
.
Please use beforeEach(TestData) instead.
Stackable trait that can be mixed into suites that need code executed before and after running each test.
BeforeAndAfterEach
when you want to stack traits that perform side-effects before and/or after tests, rather than at the beginning or end of tests, or when you need access to the config map or test name in the before and/or after code. Note: For more insight into whereBeforeAndAfterEach
fits into the big picture, see the Shared fixtures section in the documentation for your chosen style trait.A test fixture is composed of the objects and other artifacts (files, sockets, database connections, etc.) tests use to do their work. When multiple tests need to work with the same fixtures, it is important to try and avoid duplicating the fixture code across those tests. The more code duplication you have in your tests, the greater drag the tests will have on refactoring the actual production code. Trait
BeforeAndAfterEach
offers one way to eliminate such code duplication: abeforeEach
method that will be run before each test (like JUnit'ssetUp
), and anafterEach
method that will be run after (like JUnit'stearDown
).Here's an example:
To get the same ordering as
withFixture
, place yoursuper.beforeEach
call at the end of eachbeforeEach
method, and thesuper.afterEach
call at the beginning of eachafterEach
method, as shown in the previous example. It is a good idea to invokesuper.afterEach
in atry
block and perform cleanup in afinally
clause, as shown in the previous example, because this ensures the cleanup code is performed even ifsuper.afterEach
throws an exception.Besides enabling trait stacking, the other main advantage of
BeforeAndAfterEach
overBeforeAndAfter
is thatBeforeAndAfterEach
allows you to make use of test data (the test name and the config map) in your before and/or after code, whereasBeforeAndAfter
does not. To access the test data, simply override the form ofbeforeEach
and/orafterEach
that takes aTestData
parameter, like this.The main disadvantage of
BeforeAndAfterEach
compared toBeforeAndAfter
is thatBeforeAndAfterEach
requires more boilerplate. If you don't need trait stacking or access to the test data, useBeforeAndAfter
instead ofBeforeAndAfterEach
.