Test Post-Processors
Several of the post-processors available with pulse™ are used to extract test results from artifacts. These processors are known as test post-processors. As these processors perform a common task, they all share common attributes. These attributes are documented below.
Attributes
| Attribute |
Description |
Required? |
Default |
| fail-on-failure |
If true, the build will be failed when any test case failure is found. |
No |
true |
| resolve-conflicts |
Determines how to resolve conflicting test cases (two cases with identical names). Possible resolutions are:
- off: conflicting tests are combined into one test with the most severe result (e.g. failure preferred to success)
- append: conflicting names are resolved by appending an integer to the later test name (the integer is incremented until a unique name is found)
- prepend: conflicting names are resolved by prepending an integer to the later test name (the integer is incremented until a unique name is found)
|
No |
off |
| suite |
If a suite is specified, all tests found by this processor will be added to that suite. |
No |
|
Child Elements
None.
Examples
Two separate JUnit processors that will add their results to different top level suites:
<junit.pp name="junit1" suite="suite1"/>
<junit.pp name="junit2" suite="suite2"/>
