build(deps): bump serenity.version from 3.6.23 to 4.2.6

[dependabot]

Bumps serenity.version from 3.6.23 to 4.2.6.
Updates net.serenity-bdd:serenity-core from 3.6.23 to 4.2.6

Release notes

Sourced from net.serenity-bdd:serenity-core's releases.

v4.0.1

Serenity 4 Release Notes

Serenity 4.0.1 is a major upgrade. The most significant change is updating the library to support Java 11, in line with other popular testing libraries such as Selenium and Mockito. However, the migration to Java 11 requires changes in the module structure, which requires some breaking changes to the package structure.

These release notes will explain how to update your project to work with Serenity BDD 4.x.

The biggest change is the main Serenity annotations, such as @Step, which are now in the net.serenitybdd.annotations package, rather than the net.thucydides.core.annotations package as was previously the case.

If you are using Serenity internal classes, some of these may have moved as well.

The following table indicates the main changes:

Package changes

Module	Old packages	New Packages
serenity-screenplay-webdriver	net.serenity.screenplay.*	net.serenity.screenplay.webdriver.*
	net.serenitybdd.screenplay.webtest.actions.*	net.serenitybdd.screenplay.webdriver.actions.*
serenity-model	net.serenitybdd.core.*	net.serenitybdd.model.*
	net.thucydides.core.annotations.*	net.serenitybdd.annotations.*
	Other net.thucydides.core.*	net.thucydides.model.*

For example:

• Replace any annotations previously in net.thucydides.core.annotations (e.g. @​Step) in net.serenitybdd.annotations
• Replace net.thucydides.core.util.EnvironmentVariables with net.thucydides.model.util.EnvironmentVariables

This release also includes support for Selenium 4.11.0, a number of bug fixes, and improved support of reporting step durations for parallel tests.

Guice is no longer used

Serenity stopped using Guice in version 3.9.8. This has no impact on most test scripts, but if you are using internal classes such as net.thucydides.core.guice.Injectors classes to retrieve objects such as EnvironmentVariables, this will no longer work. In Serenity 4.0.0 or higher, to retrieve the current environment variables, use the net.serenitybdd.core.di.SerenityInfrastructure class as shown here:

EnvironmentVariables environmentVariables = SerenityInfrastructure.getEnvironmentVariables();

Report Generation Changes

In Serenity 4.0.x, test execution generates JSON test output files, but not HTML files. To generate the full HTML reports, invoke the aggregate task, e.g. mvn aggregate or gradle aggregate.

Commits

• 126f4f2 [ci skip] prepare release 4.2.6
• c3a2942 fix: throw exception immediately (#3558)
• 9876839 [ci skip] prepare for next development iteration
• 7700be7 [ci skip] prepare release 4.2.5
• 720f967 Fixed an edge case
• c9e3493 [ci skip] prepare for next development iteration
• 9ef3f63 [ci skip] prepare release 4.2.4
• 6e901a2 Updated Selenium
• d006369 Merge branch 'main' of https://github.com/serenity-bdd/serenity-core
• 034c971 Fix for #3258 - Handle path related issues in Windows (#3560)
• Additional commits viewable in compare view

Updates net.serenity-bdd:serenity-spring from 3.6.23 to 4.2.6

Release notes

Sourced from net.serenity-bdd:serenity-spring's releases.

v4.0.1

Serenity 4 Release Notes

Serenity 4.0.1 is a major upgrade. The most significant change is updating the library to support Java 11, in line with other popular testing libraries such as Selenium and Mockito. However, the migration to Java 11 requires changes in the module structure, which requires some breaking changes to the package structure.

These release notes will explain how to update your project to work with Serenity BDD 4.x.

The biggest change is the main Serenity annotations, such as @Step, which are now in the net.serenitybdd.annotations package, rather than the net.thucydides.core.annotations package as was previously the case.

If you are using Serenity internal classes, some of these may have moved as well.

The following table indicates the main changes:

Package changes

Module	Old packages	New Packages
serenity-screenplay-webdriver	net.serenity.screenplay.*	net.serenity.screenplay.webdriver.*
	net.serenitybdd.screenplay.webtest.actions.*	net.serenitybdd.screenplay.webdriver.actions.*
serenity-model	net.serenitybdd.core.*	net.serenitybdd.model.*
	net.thucydides.core.annotations.*	net.serenitybdd.annotations.*
	Other net.thucydides.core.*	net.thucydides.model.*

For example:

• Replace any annotations previously in net.thucydides.core.annotations (e.g. @​Step) in net.serenitybdd.annotations
• Replace net.thucydides.core.util.EnvironmentVariables with net.thucydides.model.util.EnvironmentVariables

This release also includes support for Selenium 4.11.0, a number of bug fixes, and improved support of reporting step durations for parallel tests.

Guice is no longer used

Serenity stopped using Guice in version 3.9.8. This has no impact on most test scripts, but if you are using internal classes such as net.thucydides.core.guice.Injectors classes to retrieve objects such as EnvironmentVariables, this will no longer work. In Serenity 4.0.0 or higher, to retrieve the current environment variables, use the net.serenitybdd.core.di.SerenityInfrastructure class as shown here:

EnvironmentVariables environmentVariables = SerenityInfrastructure.getEnvironmentVariables();

Report Generation Changes

In Serenity 4.0.x, test execution generates JSON test output files, but not HTML files. To generate the full HTML reports, invoke the aggregate task, e.g. mvn aggregate or gradle aggregate.

Commits

• 126f4f2 [ci skip] prepare release 4.2.6
• c3a2942 fix: throw exception immediately (#3558)
• 9876839 [ci skip] prepare for next development iteration
• 7700be7 [ci skip] prepare release 4.2.5
• 720f967 Fixed an edge case
• c9e3493 [ci skip] prepare for next development iteration
• 9ef3f63 [ci skip] prepare release 4.2.4
• 6e901a2 Updated Selenium
• d006369 Merge branch 'main' of https://github.com/serenity-bdd/serenity-core
• 034c971 Fix for #3258 - Handle path related issues in Windows (#3560)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud