- Putting last error logs of tests to Items' description, by @utdacc
- Client version updated on 5.2.13, by @HardNorth
- Client version updated on 5.2.11, by @HardNorth
- Client version updated on 5.2.4, by @HardNorth
commons-model
dependency to rely onclinet-java
exclusions in security fixes, by @HardNorth
- Client version updated on 5.2.1, by @HardNorth
- Client version updated on 5.1.16, by @HardNorth
- JUnit-Foundation updated on 17.0.2, by @HardNorth
commons-text
transitive dependency was forcibly updates to avoid critical vulnerability, by @HardNorth
- Test Case ID templating, by @HardNorth
- Client version updated on 5.1.9, by @HardNorth
- JUnit-Foundation updated on 15.3.5, by @HardNorth
- Slf4j version updated on 1.7.36, by @HardNorth
- Class level
@Attributes
annotation support
- Version promoted to stable release
- Client version updated on 5.1.0
- JUnit-Foundation updated on 15.3.4
- Service location step in documentation
- Service location file
ReportPortalListener.buildFinishStepRq(Object, FrameworkMethod, ReflectiveCallable, ItemStatus)
method
- Client version updated on 5.1.0-RC-12
- ItemTree retrieve by test Description
- Client version updated on 5.1.0-RC-6
- Version changed on 5.1.0
- Client version updated on 5.1.0-ALPHA-5
- JUnit Theories support (special thanks to Scott Babcock and JUnit Foundation)
- Powermock support (special thanks to Scott Babcock and JUnit Foundation)
- JUnit-Foundation updated on 12.5.3
- Client version updated on 5.0.18
- Parent Item status evaluation was moved into the client
- "Not Issue" issue moved into the client
- Manual Step Reporting feature
- A test status switch from PASSED to FAILED in case of an
@After
method failed - A test status when AssumptionViolatedException was thrown in
@Before
method
- JUnit Theories feature is not functioning due to upstream library exception failures: JUnit-Foundation #78
- PowerMock library is not supported due to upstream library incompatibility (issue #66). Upstream library issue: JUnit-Foundation #77
- A test status when AssumptionViolatedException was thrown. Now it marks as 'SKIPPED' (issue #63)
- JUnit Categories now handled as RP tags
- Callback reporting feature
- ExpectedException Rule handling (issue #64)
- Client version updated on 5.0.15
- Handling of standard and JUnitParams parameters without
ArtifactParams
interface
- parameterized Test Case ID generation for standard parameters (
@ParameterKey
annotation handling) - 'retrieveLeaf' and 'stopRunner' methods do not start new launch in case of empty suites / tests
- 'stopLaunch' method does not start new launch in case of there was no any tests passed
- Client version updated on 5.0.14
- Class type item level was changed from 'SUITE' to 'TEST'
- A skipped test method reporting in case of a
@Before
method failed
- A null-pointer exception on
@Before
methods
- ParallelRunningHandler class was deleted due to redundancy, all its logic moved to ReportPortalListener class
- A test retry feature which is based on corresponding JunitFoundation's feature.
@Ignore
annotation support
- JunitFoundation version was updated on 12.3.0
- Parameters extraction logic moved into the client, now it works in the same way as for other agents
- Test Case ID logic moved into the client, now it also works in the same way as for other agents
- Code reference generation logic moved into client
- Test reporting structure now conforms with other agents
- Client version updated on 5.0.13
- Some protected methods for extensions implementation were removed due to their redundancy. Alternative methods for extensions will be added in further implementation.