Neodymium 5.3.0

Neodymium 5.3.0 is a stability-focused release. Alongside several new features, this version resolves a variety of reported issues to further improve the reliability and flexibility of your test automation.

5.3.0

Highlights

  • Retry Flaky Tests: New @Retry annotation to stabilize tests against transient errors.
  • Data Set Ranges: Execute specific subsets of data using ranges like @DataSet((3,16)).
  • CI/CD Flexibility: New property to filter browsers directly from your pipeline.
  • Stability: Major fixes for video recording during alerts, Lighthouse audits, and JUnit 5 lifecycle methods.

Details

  • Feature: Retry Flaky Tests
    • Flaky tests can drain productivity and undermine confidence in test reports. To stabilize these, we introduced the @Retry annotation. This allows you to automatically retry a test when specific error messages are encountered.
  • Feature: Data Set Ranges
    • Managing large volumes of data sets is now easier. You can now execute tests for a specific range of data using @DataSet((3,16)), which will run the test using data sets 3 through 16.
  • Feature: Test Filtering
    • Added the property neodymium.webDriver.browserFilter to enable or disable specific browsers directly via your CI/CD pipeline.
  • Fix #335: Resolved an issue where the URL filter incorrectly excluded certain paths.
  • Fix #341: Added a configuration option for viewport highlighting. Previously, the non-viewport area was always blurred, which could obscure important error messages.
  • Fix #354: Fixed a JSON structure mismatch that caused Lighthouse audit assertions to miss certain list items.
  • Fix #355: The Neodymium random seed now resets correctly after a test run, allowing for the rerunning of individual tests with the same seed.
  • Fix #356: Fixed a regression where the configuration to take a screenshot on every step was not working.
  • Fix #360: Ensured all test data retrieval methods correctly include data as an attachment in the report.
  • Fix #363: Fixed an issue where tests without a specific browser configuration defaulted to a Selenide WebDriver that lacked Neodymium features. @Browser now correctly enables the default browser with full video support.
  • Fix #364: Fixed property substitution within the Allure environment section.
  • Fix #369: Improved the pop-up blocker to support SVG links and optimized the overall implementation.
  • Fix #390: Added a workaround for the test data report view to handle long values exceeding the JavaScript number range.
  • Fix #393: Resolved compatibility issues with JUnit 5 beforeEach and afterEach methods.
  • Fix #383: The default browser now automatically suppresses Chrome’s password-saving warnings to prevent interference with test execution.
  • Fix #396: Fixed a bug where open alerts would cause video recording to fail.
  • Fix #397: Corrected a system property issue that prevented enabling/disabling browsers from a CI/CD pipeline.
  • Fix #357: Updated documentation and internal references to remove links to the old repository name.
  • Fix #402: Resolved an issue where full-page screenshots caused video resolution inconsistencies.
  • Fix #417: Video recording now automatically pauses while an alert is open, as browsers cannot record during active modal alerts.
  • Fix #416: Fixed an issue where a failed video attachment could cause associated test data to be missing from the report.
  • Fix #431: Fixed a bug preventing the detection of the Firefox binary within the Windows PATH.
Last modified March 6, 2026: Update v5_3_0.md (b1d1f3b5)