Returns an Alerter
that during test execution will forward strings (and other objects) passed to its
apply
method to the current reporter.
Returns an Alerter
that during test execution will forward strings (and other objects) passed to its
apply
method to the current reporter. If invoked in a constructor, it
will register the passed string for forwarding later during test execution. If invoked while this
AnyPropSpec
is being executed, such as from inside a test function, it will forward the information to
the current reporter immediately. If invoked at any other time, it will
print to the standard output. This method can be called safely by any thread.
Register a property-based test to ignore, which has the specified name, optional tags, and function value that takes no arguments.
Register a property-based test to ignore, which has the specified name, optional tags, and function value that takes no arguments.
This method will register the test for later ignoring via an invocation of one of the run
methods. This method exists to make it easy to ignore an existing test by changing the call to test
to ignore
without deleting or commenting out the actual test code. The test will not be run, but a
report will be sent that indicates the test was ignored. The passed test name must not have been registered previously on
this AnyPropSpec
instance.
the name of the test
the optional list of tags for this test
the test function
if a test with the same name has been registered previously
NotAllowedExceptionif testName
had been registered previously
if invoked after run
has been invoked on this suite
Returns an Informer
that during test execution will forward strings passed to its
apply
method to the current reporter.
Returns an Informer
that during test execution will forward strings passed to its
apply
method to the current reporter. If invoked in a constructor, it
will register the passed string for forwarding later during test execution. If invoked from inside a scope,
it will forward the information to the current reporter immediately. If invoked from inside a test function,
it will record the information and forward it to the current reporter only after the test completed, as recordedEvents
of the test completed event, such as TestSucceeded
. If invoked at any other time, it will print to the standard output.
This method can be called safely by any thread.
Returns a Documenter
that during test execution will forward strings passed to its
apply
method to the current reporter.
Returns a Documenter
that during test execution will forward strings passed to its
apply
method to the current reporter. If invoked in a constructor, it
will register the passed string for forwarding later during test execution. If invoked from inside a scope,
it will forward the information to the current reporter immediately. If invoked from inside a test function,
it will record the information and forward it to the current reporter only after the test completed, as recordedEvents
of the test completed event, such as TestSucceeded
. If invoked at any other time, it will print to the standard output.
This method can be called safely by any thread.
Returns a Notifier
that during test execution will forward strings (and other objects) passed to its
apply
method to the current reporter.
Returns a Notifier
that during test execution will forward strings (and other objects) passed to its
apply
method to the current reporter. If invoked in a constructor, it
will register the passed string for forwarding later during test execution. If invoked while this
AnyPropSpec
is being executed, such as from inside a test function, it will forward the information to
the current reporter immediately. If invoked at any other time, it will
print to the standard output. This method can be called safely by any thread.
Registers shared tests.
Registers shared tests.
This method enables the following syntax for shared tests in a AnyPropSpec
:
propertiesFor(nonEmptyStack(lastValuePushed))
This method just provides syntax sugar intended to make the intent of the code clearer.
Because the parameter passed to it is
type Unit
, the expression will be evaluated before being passed, which
is sufficient to register the shared tests. For examples of shared tests, see the
Shared tests section in the main documentation for this trait.
Register a property-based test with the specified name, optional tags, and function value that takes no arguments.
Register a property-based test with the specified name, optional tags, and function value that takes no arguments.
This method will register the test for later execution via an invocation of one of the run
methods. The passed test name must not have been registered previously on
this AnyPropSpec
instance.
the name of the property
the optional list of tags for this property
the property function
if a test with the same name has been registered previously
NotAllowedExceptionif testName
had been registered previously
if testName
or any passed test tag is null
if invoked after run
has been invoked on this suite
Run a test.
Run a test. This trait's implementation runs the test registered with the name specified by testName
.
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 .
if testName
is defined but a test with that name does not exist on this AnyPropSpec
if any of testName
, reporter
, stopper
, or configMap
is null
.
Run zero to many of this AnyPropSpec
's tests.
Run zero to many of this AnyPropSpec
'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.
if testName
is defined, but no test with the specified test name
exists in this Suite
if any of the passed parameters is null
.
A Map
whose keys are String
names of tagged tests and whose associated values are
the Set
of tags for the test.
A Map
whose keys are String
names of tagged tests and whose associated values are
the Set
of tags for the test. If this AnyPropSpec
contains no tags, this method returns an empty Map
.
This trait's implementation returns tags that were passed as strings contained in Tag
objects passed to
methods property
and ignore
.
In addition, this trait's implementation will also auto-tag tests 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
org.scalatest.Ignore
.
An immutable Set
of test names.
An immutable Set
of test names. If this AnyPropSpec
contains no tests, this method returns an empty Set
.
This trait's implementation of this method will return a set that contains the names of all registered tests. The set's iterator will return those names in the order in which the tests were registered.
Returns a user friendly string for this suite, composed of the
simple name of the class (possibly simplified further by removing dollar signs if added by the Scala interpeter) and, if this suite
contains nested suites, the result of invoking toString
on each
of the nested suites, separated by commas and surrounded by parentheses.
Returns a user friendly string for this suite, composed of the
simple name of the class (possibly simplified further by removing dollar signs if added by the Scala interpeter) and, if this suite
contains nested suites, the result of invoking toString
on each
of the nested suites, separated by commas and surrounded by parentheses.
a user-friendly string for this suite
(Since version 3.1.0) The conversionCheckedConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
(Since version 3.1.0) The convertEquivalenceToAToBConversionConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
(Since version 3.1.0) The convertEquivalenceToBToAConversionConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
(Since version 3.1.0) The lowPriorityConversionCheckedConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
The styleName
lifecycle method has been deprecated and will be removed in a future version of ScalaTest.
The styleName
lifecycle method has been deprecated and will be removed in a future version of ScalaTest.
This method was used to support the chosen styles feature, which was deactivated in 3.1.0. The internal modularization of ScalaTest in 3.2.0
will replace chosen styles as the tool to encourage consistency across a project. We do not plan a replacement for styleName
.
(Since version 3.1.0) The styleName lifecycle method has been deprecated and will be removed in a future version of ScalaTest with no replacement.
A suite of property-based tests.
AnyPropSpec
is a good fit for teams that want to write tests exclusively in terms of property checks, and is also a good choice for writing the occasional test matrix when a different style trait is chosen as the main unit testing style.Here's an example
AnyPropSpec
:You can run a
AnyPropSpec
by invokingexecute
on it. This method, which prints test results to the standard output, is intended to serve as a convenient way to run tests from within the Scala interpreter. For example, to runSetSpec
from within the Scala interpreter, you could write:And you would see:
SetSpec: - an empty Set should have size 0 - invoking head on an empty Set should produce NoSuchElementException
Or, to run just the “
an empty Set should have size 0
” method, you could pass that test's name, or any unique substring of the name, such as"size 0"
or even just"0"
. Here's an example:scala> org.scalatest.run(new SetSpec, "size 0") SetSpec: - an empty Set should have size 0
You can also pass to
execute
a config map of key-value pairs, which will be passed down into suites and tests, as well as other parameters that configure the run itself. For more information on running in the Scala interpreter, see the documentation forexecute
(below) and the ScalaTest shell.The
execute
method invokes arun
method that takes two parameters. Thisrun
method, which actually executes the suite, will usually be invoked by a test runner, such asrun
,tools.Runner
, a build tool, or an IDE.“
property
” is a method, defined inAnyPropSpec
, which will be invoked by the primary constructor ofSetSpec
. You specify the name of the test as a string between the parentheses, and the test code itself between curly braces. The test code is a function passed as a by-name parameter toproperty
, which registers it for later execution.A
AnyPropSpec
's lifecycle has two phases: the registration phase and the ready phase. It starts in registration phase and enters ready phase the first timerun
is called on it. It then remains in ready phase for the remainder of its lifetime.Tests can only be registered with the
property
method while theAnyPropSpec
is in its registration phase. Any attempt to register a test after theAnyPropSpec
has entered its ready phase, i.e., afterrun
has been invoked on theAnyPropSpec
, will be met with a thrownTestRegistrationClosedException
. The recommended style of usingAnyPropSpec
is to register tests during object construction as is done in all the examples shown here. If you keep to the recommended style, you should never see aTestRegistrationClosedException
.Ignored tests
To support the common use case of temporarily disabling a test, with the good intention of resurrecting the test at a later time,
AnyPropSpec
provides registration methods that start withignore
instead ofproperty
. Here's an example:If you run this version of
SetSuite
with:It will run only the second test and report that the first test was ignored:
Informers
One of the parameters to
AnyPropSpec
'srun
method is aReporter
, which will collect and report information about the running suite of tests. Information about suites and tests that were run, whether tests succeeded or failed, and tests that were ignored will be passed to theReporter
as the suite runs. Most often the reporting done by default byAnyPropSpec
's methods will be sufficient, but occasionally you may wish to provide custom information to theReporter
from a test. For this purpose, anInformer
that will forward information to the currentReporter
is provided via theinfo
parameterless method. You can pass the extra information to theInformer
via itsapply
method. TheInformer
will then pass the information to theReporter
via anInfoProvided
event. Here's an example that shows both a direct use as well as an indirect use through the methods ofGivenWhenThen
:If you run this
AnyPropSpec
from the interpreter, you will see the following output:scala> org.scalatest.run(new SetSpec) SetSpec: - an element can be added to an empty mutable Set + ---------------- + Given an empty mutable BitSet + When an element is added + Then the Set should have size 1 + And the Set should contain the added element + ---------------- + Given an empty mutable HashSet + When an element is added + Then the Set should have size 1 + And the Set should contain the added element + ---------------- + Given an empty mutable LinkedHashSet + When an element is added + Then the Set should have size 1 + And the Set should contain the added element
Documenters
AnyPropSpec
also provides amarkup
method that returns aDocumenter
, which allows you to send to theReporter
text formatted in Markdown syntax. You can pass the extra information to theDocumenter
via itsapply
method. TheDocumenter
will then pass the information to theReporter
via anMarkupProvided
event.Here's an example
AnyPropSpec
that usesmarkup
:Although all of ScalaTest's built-in reporters will display the markup text in some form, the HTML reporter will format the markup information into HTML. Thus, the main purpose of
markup
is to add nicely formatted text to HTML reports. Here's what the aboveSetSpec
would look like in the HTML reporter:Notifiers and alerters
ScalaTest records text passed to
info
andmarkup
during tests, and sends the recorded text in therecordedEvents
field of test completion events likeTestSucceeded
andTestFailed
. This allows string reporters (like the standard out reporter) to showinfo
andmarkup
text after the test name in a color determined by the outcome of the test. For example, if the test fails, string reporters will show theinfo
andmarkup
text in red. If a test succeeds, string reporters will show theinfo
andmarkup
text in green. While this approach helps the readability of reports, it means that you can't useinfo
to get status updates from long running tests.To get immediate (i.e., non-recorded) notifications from tests, you can use
note
(aNotifier
) andalert
(anAlerter
). Here's an example showing the differences:Because
note
andalert
information is sent immediately, it will appear before the test name in string reporters, and its color will be unrelated to the ultimate outcome of the test:note
text will always appear in green,alert
text will always appear in yellow. Here's an example:Another example is slowpoke notifications. If you find a test is taking a long time to complete, but you're not sure which test, you can enable slowpoke notifications. ScalaTest will use an
Alerter
to fire an event whenever a test has been running longer than a specified amount of time.In summary, use
info
andmarkup
for text that should form part of the specification output. Usenote
andalert
to send status notifications. (Because the HTML reporter is intended to produce a readable, printable specification,info
andmarkup
text will appear in the HTML report, butnote
andalert
text will not.)Pending tests
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, 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 with
TestPendingException
, both the test name and any information sent to the reporter when running the test can appear in the report of a test run. (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.You can mark tests pending in
AnyPropSpec
like this:(Note: "
(pending)
" is the body of the test. Thus the test contains just one statement, an invocation of thepending
method, which throwsTestPendingException
.) If you run this version ofSetSuite
with:It will run both tests, but report that first test is pending. You'll see:
One difference between an ignored test and a pending one is that an ignored test is intended to be used during a significant refactorings of the code under test, when tests break and you don't want to spend the time to fix all of them immediately. You can mark some of those broken tests as ignored temporarily, so that you can focus the red bar on just failing tests you actually want to fix immediately. Later you can go back and fix the ignored tests. In other words, by ignoring some failing tests temporarily, you can more easily notice failed tests that you actually want to fix. By contrast, a pending test is intended to be used before a test and/or the code under test is written. Pending indicates you've decided to write a test for a bit of behavior, but either you haven't written the test yet, or have only written part of it, or perhaps you've written the test but don't want to implement the behavior it tests until after you've implemented a different bit of behavior you realized you need first. Thus ignored tests are designed to facilitate refactoring of existing code whereas pending tests are designed to facilitate the creation of new code.
One other difference between ignored and pending tests is that ignored tests are implemented as a test tag that is excluded by default. Thus an ignored test is never executed. By contrast, a pending test is implemented as a test that throws
TestPendingException
(which is what calling thepending
method does). Thus the body of pending tests are executed up until they throwTestPendingException
. The reason for this difference is that it enables your unfinished test to sendInfoProvided
messages to the reporter before it completes abruptly withTestPendingException
, as shown in the previous example onInformer
s that used theGivenWhenThen
trait.Tagging tests
A
AnyPropSpec
's tests may be classified into groups by tagging them with string names. As with any suite, when executing aAnyPropSpec
, groups of tests can optionally be included and/or excluded. To tag aAnyPropSpec
's tests, you pass objects that extend classorg.scalatest.Tag
to methods that register tests. ClassTag
takes one parameter, a string name. If you have created tag annotation interfaces as described in theTag
documentation, then you will probably want to use tag names on your test functions that match. To do so, simply pass the fully qualified names of the tag interfaces to theTag
constructor. For example, if you've defined a tag annotation interface with fully qualified names,com.mycompany.tags.DbTest
, then you could create a matching tag forAnyPropSpec
s like this:Given these definitions, you could place
AnyPropSpec
tests into groups with tags like this:This code marks both tests with the
org.scalatest.tags.Slow
tag, and the second test with thecom.mycompany.tags.DbTest
tag.The
run
method takes aFilter
, whose constructor takes an optionalSet[String]
calledtagsToInclude
and aSet[String]
calledtagsToExclude
. IftagsToInclude
isNone
, all tests will be run except those those belonging to tags listed in thetagsToExclude
Set
. IftagsToInclude
is defined, only tests belonging to tags mentioned in thetagsToInclude
set, and not mentioned intagsToExclude
, will be run.Shared fixtures
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.
ScalaTest recommends three techniques to eliminate such code duplication:
withFixture
Each technique is geared towards helping you reduce code duplication without introducing instance
var
s, shared mutable objects, or other dependencies between tests. Eliminating shared mutable state across tests will make your test code easier to reason about and more amenable for parallel test execution.The techniques in
AnyPropSpec
are identical to those inFunSuite
, but with “test
” replaced by “property
”. The following table summarizes the options with a link to the relevant documentation for traitFunSuite
:withFixture
when most or all tests need the same fixture.withFixture(NoArgTest)
withFixture(OneArgTest)
instead)withFixture(OneArgTest)
BeforeAndAfter
BeforeAndAfterEach
Using
AnyPropSpec
to implement a test matrixUsing fixture-context objects in a
AnyPropSpec
is a good way to implement a test matrix. What is the matrix? A test matrix is a series of tests that you need to run on a series of subjects. For example, The Scala API contains many implementations of traitSet
. Every implementation must obey the contract ofSet
. One property of anySet
is that an emptySet
should have size 0, another is that invoking head on an emptySet
should give you aNoSuchElementException
, and so on. Already you have a matrix, where rows are the properties and the columns are the set implementations:BitSet
HashSet
TreeSet
One way to implement this test matrix is to define a trait to represent the columns (in this case,
BitSet
,HashSet
, andTreeSet
) as elements in a single-dimensionalTable
. Each element in theTable
represents oneSet
implementation. Because different properties may require different fixture instances for those implementations, you can define a trait to hold the examples, like this:Given this trait, you could provide empty sets in one implementation of
SetExamples
, and non-empty sets in another. Here's how you might provide empty set examples:And here's how you might provide set examples with one item each:
Armed with these example classes, you can define checks of properties that require empty or non-empty set fixtures by using instances of these classes as fixture-context objects. In other words, the columns of the test matrix are implemented as elements of a one-dimensional table of fixtures, the rows are implemented as
property
clauses of aAnyPropSpec
.Here's a complete example that checks the two properties mentioned previously:
One benefit of this approach is that the compiler will help you when you need to add either a new row or column to the matrix. In either case, you'll need to ensure all cells are checked to get your code to compile.
Shared tests
Sometimes you may want to run the same test code on different fixture objects. That is to say, you may want to write tests that are "shared" by different fixture objects. You accomplish this in a
AnyPropSpec
in the same way you would do it in aFunSuite
, except instead oftest
you sayproperty
, and instead oftestsFor
you saypropertiesFor
. For more information, see the Shared tests section ofFunSuite
's documentation.