The SpecsStats class just stores a list of stats, each one corresponding to a Fragment
The SpecsStats class just stores a list of stats, each one corresponding to a Fragment
The SpecsStatistics class stores the result of a specification execution, with the a list of 'current' stats for each fragment execution and the total statistics for the whole specification
The SpecsStatistics class stores the result of a specification execution, with the a list of 'current' stats for each fragment execution and the total statistics for the whole specification
arguments for the specification
map providing a description for each fragment
the junit notifier to use
system properties
the selected fragments to report
an Example which body comes from the execution of that example in a brand new instance of the Specification
execute sequences of Fragments.
execute sequences of Fragments.
If the stopOnFail argument is true, we check that the execution is ok before executing the next sequence.
execute a Fragment.
execute a Fragment.
A Form is executed separately by executing each row and cell, setting the results on each cell
This method could be overriden to provide alternate behavior when executing an Example
This method could be overriden to provide alternate behavior when executing an Example
execute a Fragment.
execute a Fragment.
a function exporting an ExecutingSpecification
filter fragments depending on the command line arguments and the current arguments in the specification
the filter method filters examples based on their description, keeping only the ones matching the ex attribute of the arguments object
the filter method filters examples based on their description, keeping only the ones matching the ex attribute of the arguments object
fragments according to their previous execution state
filter fragments according to tags by collecting tags as applicable to each fragment and applying them
This method is used to determine for example if the JUnit runner is executed from Maven or within Eclipse.
This method is used to determine for example if the JUnit runner is executed from Maven or within Eclipse. In the first the test case names don't need to have the hashcode example.
true if the this current piece of code contains name in its stacktrace.
return true if the current test is executed from an IDE
return true if the current test is executed from an IDE
return true if the current test is executed with eclipse
return true if the current test is executed with eclipse
return true if the current test is executed with Gradle
return true if the current test is executed with Gradle
return true if the current test is executed with Intellij
return true if the current test is executed with Intellij
return true if the current test is executed with Maven
return true if the current test is executed with Maven
return true if the current test is executed with sbt
return true if the current test is executed with sbt
This function "clones" the body of each example if the applicable arguments indicate that the specification should be isolated
This function "clones" the body of each example if the applicable arguments indicate that the specification should be isolated
run the suite by executing each fragment related to a description: - execute all fragments (including Steps which are reported as steps) - for each result, report the failure/error/skipped or pending message as a junit failure or ignored event on the RunNotifier
report Fragments by:
report Fragments by:
the reporter
select function returning a filtered seq of Fragments
select function returning a filtered seq of Fragments
select function returning a filtered seq of Fragments
select function returning a filtered seq of Fragments
the sequence method returns sequences of fragments which can be executed concurrently.
the sequence method returns sequences of fragments which can be executed concurrently. Among the constraints to respect, any Step Fragment must be executed before any following Example Fragment, so that "first" and "last" actions are executed properly in a Specification
If the arguments specify that the specification is sequential, then each fragment will be executed individually
sequence function returning an ordered seq of seq of Fragments
sequence function returning an ordered seq of seq of Fragments
set the statistics on SpecEndFragments after they've been computed by the StatisticsReducer Those statistics are updated from previously executed statistics to calculate trends
set the statistics on SpecEndFragments after they've been computed by the StatisticsReducer Those statistics are updated from previously executed statistics to calculate trends
a function storing ExecutedFragments
store the results by spec name
store the results by spec name
store the statistics: - for SpecEnd -> put the stats in the repository - for a SpecStart that's a link -> read the status of the previous execution
store the statistics: - for SpecEnd -> put the stats in the repository - for a SpecStart that's a link -> read the status of the previous execution
From a Seq of Fragments create a seq of corresponding tags for each fragment, considering that:
From a Seq of Fragments create a seq of corresponding tags for each fragment, considering that:
TaggedAs fragment is applicable to the the previous fragmentTag fragment is applicable to the the next fragmentAsSection fragment is applicable to the the previous fragment to the next AsSection fragment with the same nameSection fragment is applicable to the the next fragment to the next Section fragment with the same name
The JUnitReporter reports a specification by using a JUnit RunNotifier
To do so, it uses most of the execution pipeline of a normal reporter but overrides the fragments execution so as to notify JUnit of the appropriate events