Returns an Alerter 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 while this PathAnyFreeSpec 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.

Supports shared test registration in PathAnyFreeSpecs.

This field enables syntax such as the following:

behave like nonFullStack(stackWithOneItem)
^

For more information and examples of the use of <cod>behave, see the Shared tests section in the main documentation for sister trait org.scalatest.freespec.PathAnyFreeSpec.

Implicitly converts Strings to FreeSpecStringWrapper, which enables methods in, is, taggedAs and ignore, as well as the dash operator (-), to be invoked on Strings.

The total number of tests that are expected to run when this PathAnyFreeSpec's run method is invoked.

This trait's implementation of this method will first ensure that the results of all tests, each run its its own instance executing only the path to the test, are registered. For details on this process see the How it executes section in the main documentation for this trait.

This trait's implementation of this method returns the size of the testNames List, minus the number of tests marked as ignored as well as any tests excluded by the passed Filter.

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

Returns an Informer that during test execution will forward strings (and other objects) passed to its apply method to the current reporter. If invoked in a constructor (including within a test, since those are invoked during construction in a PathAnyFreeSpec, it will register the passed string for forwarding later when run is invoked. 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 (and other objects) passed to its apply method to the current reporter. If invoked in a constructor (including within a test, since those are invoked during construction in a PathAnyFreeSpec, it will register the passed string for forwarding later when run is invoked. 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 an empty list.

This lifecycle method is unused by this trait. If invoked, it will return an empty list, because nested suites are not allowed in a PathAnyFreeSpec. Because a PathAnyFreeSpec executes tests eagerly at construction time, registering the results of those test runs and reporting them later, the order of nested suites versus test runs would be different in a org.scalatest.freespec.PathAnyFreeSpec than in an org.scalatest.freespec.AnyFreeSpec. In an org.scalatest.freespec.AnyFreeSpec, nested suites are executed then tests are executed. In an org.scalatest.freespec.PathAnyFreeSpec it would be the opposite. To make the code easy to reason about, therefore, this is just not allowed. If you want to add nested suites to a PathAnyFreeSpec, you can instead wrap them all in a Suites object and put them in whatever order you wish.

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

Returns a Notifier 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 while this Path.FreeSpec 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.

Runs this path.FreeSpec, reporting test results that were registered when the tests were run, each during the construction of its own instance.

This trait's implementation of this method will first ensure that the results of all tests, each run its its own instance executing only the path to the test, are registered. For details on this process see the How it executes section in the main documentation for this trait.

If testName is None, this trait's implementation of this method will report the registered results for all tests except any excluded by the passed Filter. If testName is defined, it will report the results of only that named test. Because a path.FreeSpec is not allowed to contain nested suites, this trait's implementation of this method does not call runNestedSuites.

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

This lifecycle method is unused by this trait, and is implemented to do nothing. If invoked, it will just return immediately.

Nested suites are not allowed in a PathAnyFreeSpec. Because a PathAnyFreeSpec executes tests eagerly at construction time, registering the results of those test runs and reporting them later, the order of nested suites versus test runs would be different in a org.scalatest.freespec.PathAnyFreeSpec than in an org.scalatest.freespec.AnyFreeSpec. In an org.scalatest.freespec.AnyFreeSpec, nested suites are executed then tests are executed. In an org.scalatest.freespec.PathAnyFreeSpec it would be the opposite. To make the code easy to reason about, therefore, this is just not allowed. If you want to add nested suites to a path.FreeSpec, you can instead wrap them all in a Suites object and put them in whatever order you wish.

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

Runs a test.

This trait's implementation of this method will first ensure that the results of all tests, each run its its own instance executing only the path to the test, are registered. For details on this process see the How it executes section in the main documentation for this trait.

This trait's implementation reports the test results registered with the name specified by testName. Each test's name is a concatenation of the text of all describers surrounding a test, from outside in, and the test's spec text, with one space placed between each item. (See the documentation for testNames for an example.)

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

This lifecycle method is unused by this trait, and will complete abruptly with UnsupportedOperationException if invoked.

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

A Map whose keys are String tag names to which tests in this PathAnyFreeSpec belong, and values the Set of test names that belong to each tag. If this PathAnyFreeSpec contains no tags, this method returns an empty Map.

This trait's implementation of this method will first ensure that the results of all tests, each run its its own instance executing only the path to the test, are registered. For details on this process see the How it executes section in the main documentation for this trait.

This trait's implementation returns tags that were passed as strings contained in Tag objects passed to methods test 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 @Ignore.

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

An immutable Set of test names. If this PathAnyFreeSpec contains no tests, this method returns an empty Set.

This trait's implementation of this method will first ensure that the results of all tests, each run its its own instance executing only the path to the test, are registered. For details on this process see the How it executes section in the main documentation for this trait.

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. Each test's name is composed of the concatenation of the text of each surrounding describer, in order from outside in, and the text of the example itself, with all components separated by a space. For example, consider this PathAnyFreeSpec:

import org.scalatest.freespec

class StackSpec extends freespec.PathAnyFreeSpec {
  "A Stack" - {
    "when not empty" - {
      "must allow me to pop" in {}
    }
    "when not full" - {
      "must allow me to push" in {}
    }
  }
}

Invoking testNames on this FreeSpec will yield a set that contains the following two test name strings:

"A Stack when not empty must allow me to pop"
"A Stack when not full must allow me to push"

This trait's implementation of this method is marked as final. For insight onto why, see the Shared fixtures section in the main documentation for this trait.

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.