Neodymium v4.1.0
Ingredients for this release: 2-3 cups of features, one spoon of bug fixes and a handful documentation 🍲
Required Adoption
- Cucumber 6 no longer supports configuration via system property variables as stated in the allure documentation see (issue). So if you use Neodymium with Cucumber as BDD approach, perform the following tasks to adapt these changes in your test suite:
- Remove the following part from the
maven-surefire-plugin
plugin:
<systemPropertyVariables> <cucumber.options>--plugin io.qameta.allure.cucumber5jvm.AllureCucumber5Jvm</cucumber.options> </systemPropertyVariables>
- Option one within the test case:
@CucumberOptions( features = "src/test/java/template/cucumber/features", glue = “template", plugin = {“io.qameta.allure.cucumber6jvm.AllureCucumber6Jvm”} ) public class RunAllFeaturesTest { }
- Option two within the
src/test/resources/cucumber.properties
file:
cucumber.plugin=io.qameta.allure.cucumber6jvm.AllureCucumber6Jvm
- Remove the following part from the
Content
Features:
- Add check for test data key exists - #141 documentation
- Offer fixed random support - #85 documentation
- Print a one line Neodymium version information at runtime - #139 documentation
- Support global browser settings - #123 documentation
Improvement, Documentation and Bugfixes:
- Add How to Run Neodymium wiki page - #140 documentation
- Consolidate JavaDoc - #107 (ongoing)
- Document test execution order - #134 documentation
- Fix displaying of ignore reasons for test methods in allure report - #145
- Improve SelenideAddons.wrapAssertionError - #142
- Remove support for ftp proxy - #144
- Stabilize the SelenideAddonsTest - #143
Deprecated:
- Deprecate SelenideAddons.matchAttribute - #146:
- Please switch to
com.codeborne.selenide.Condition.attributeMatching
. - Note: You need to adapt your regex. You could add
.*
at the beginning and the end to match the current behavior (contains the given regex) or define it more precisely according to your test case.
- Please switch to
Updates: