search

Ensono / stacks-webapp-template

Templating monorepo focusing on boilerplate web apps
https://amido.github.io/stacks/
MIT License
3 stars 9 forks source link

chore(deps-dev): bump serenity.version from 2.3.4 to 3.4.2 in /packages/scaffolding-cli/templates/test/xxAMIDOxx.xxSTACKSxx.E2E.Serenity #1841

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps serenity.version from 2.3.4 to 3.4.2. Updates serenity-junit from 2.3.4 to 3.4.2

Release notes

Sourced from serenity-junit's releases.

3.2.0

Serenity 3.2.0 contains a number of bug fixes and enhancements, including:

  • Improved performance in report generation
  • Updated the Page Elements API (https://serenity-bdd.github.io/documentation/docs/guide/page_elements)
  • Improved requirements reporting to include more comprehensive requirements tables and better support for deep requirements hierarchies
  • Collections of elements retrieved with findAll() methods and then processed (e.g. findAll(".myelements").texts()) will now automatically requery if a stale element exception occurs. You can disable this behaviour by setting the webdriver.retry.on.stable.element.exception property to false.
  • Improved Playwright/Screenplay integration
  • Support for @​singlebrowser annotation in Cucumber scenarios
  • Bug fixes include:

3.1.20

Minor update including some bug fixes, performance improvements, enhanced Playwright support, and support for Selenium 4.1.2

3.1.15

This release includes support for Selenium 4.1.1 and Cucumber 7, as well as various bug fixes. We have also introduced beta support for Playwright using Screenplay.

3.1.0

Serenity 3.1.0 is a major new release of Serenity BDD. Some of the more significant changes include:

  • Integration with Selenium 4 and Appium 8
  • Improved reporting, including reporting on test duration
  • New responsive report layout
  • Use the serenity.report.accesibility property to render reports using patterns instead of plain colors
  • Filtering Cucumber scenarios (e.g. using the "cucumber.filter.tags" option will now exclude filtered features from appearing in the reports, allowing more focused reporting)
  • Added the WebDriverManagerEnhancer interface, which allows you to write custom code to integrate with the more advanced WebDriverManager features from within Serenity.
  • Chrome is now the default browser
  • Added the SingleBrowser annotation and tag which can be used in JUnit or Cucumber to run all the scenarios in a test suite, feature or scenario outline in a single browser instance
  • Added the InTheBrowser task which makes it easier to perform direct WebDriver operations from within a Screenplay task.

For more details about the new features read this article.

v2.6.0 support for JUnit 5

Serenity 2.6.0 is a major update that adds beta support for JUnit5.

  • In comparison with the JUnit4 integration, for JUnit5 tests no additional annotation is needed. Short overview of supported features/annotations
  • Tagging : @Tag("type:name") - mvn clean verify -Dtags="type:name"
  • Data Driven tests: @ParameterizedTest,@ValueSource,@EnumSource,@CsvFileSource
  • Nested tests: @Nested
  • @DisplayName for methods

The following plugins must be upgraded to the version 3.0.0-M5

  • maven-surefire-plugin
  • maven-failsafe-plugin

A big callout to @​cliviu who spearheaded this module!

... (truncated)

Commits


Updates serenity-screenplay from 2.3.4 to 3.4.2

Release notes

Sourced from serenity-screenplay's releases.

3.2.0

Serenity 3.2.0 contains a number of bug fixes and enhancements, including:

  • Improved performance in report generation
  • Updated the Page Elements API (https://serenity-bdd.github.io/documentation/docs/guide/page_elements)
  • Improved requirements reporting to include more comprehensive requirements tables and better support for deep requirements hierarchies
  • Collections of elements retrieved with findAll() methods and then processed (e.g. findAll(".myelements").texts()) will now automatically requery if a stale element exception occurs. You can disable this behaviour by setting the webdriver.retry.on.stable.element.exception property to false.
  • Improved Playwright/Screenplay integration
  • Support for @​singlebrowser annotation in Cucumber scenarios
  • Bug fixes include:

3.1.20

Minor update including some bug fixes, performance improvements, enhanced Playwright support, and support for Selenium 4.1.2

3.1.15

This release includes support for Selenium 4.1.1 and Cucumber 7, as well as various bug fixes. We have also introduced beta support for Playwright using Screenplay.

3.1.0

Serenity 3.1.0 is a major new release of Serenity BDD. Some of the more significant changes include:

  • Integration with Selenium 4 and Appium 8
  • Improved reporting, including reporting on test duration
  • New responsive report layout
  • Use the serenity.report.accesibility property to render reports using patterns instead of plain colors
  • Filtering Cucumber scenarios (e.g. using the "cucumber.filter.tags" option will now exclude filtered features from appearing in the reports, allowing more focused reporting)
  • Added the WebDriverManagerEnhancer interface, which allows you to write custom code to integrate with the more advanced WebDriverManager features from within Serenity.
  • Chrome is now the default browser
  • Added the SingleBrowser annotation and tag which can be used in JUnit or Cucumber to run all the scenarios in a test suite, feature or scenario outline in a single browser instance
  • Added the InTheBrowser task which makes it easier to perform direct WebDriver operations from within a Screenplay task.

For more details about the new features read this article.

v2.6.0 support for JUnit 5

Serenity 2.6.0 is a major update that adds beta support for JUnit5.

  • In comparison with the JUnit4 integration, for JUnit5 tests no additional annotation is needed. Short overview of supported features/annotations
  • Tagging : @Tag("type:name") - mvn clean verify -Dtags="type:name"
  • Data Driven tests: @ParameterizedTest,@ValueSource,@EnumSource,@CsvFileSource
  • Nested tests: @Nested
  • @DisplayName for methods

The following plugins must be upgraded to the version 3.0.0-M5

  • maven-surefire-plugin
  • maven-failsafe-plugin

A big callout to @​cliviu who spearheaded this module!

... (truncated)

Commits


Updates serenity-screenplay-webdriver from 2.3.4 to 3.4.2

Release notes

Sourced from serenity-screenplay-webdriver's releases.

3.2.0

Serenity 3.2.0 contains a number of bug fixes and enhancements, including:

  • Improved performance in report generation
  • Updated the Page Elements API (https://serenity-bdd.github.io/documentation/docs/guide/page_elements)
  • Improved requirements reporting to include more comprehensive requirements tables and better support for deep requirements hierarchies
  • Collections of elements retrieved with findAll() methods and then processed (e.g. findAll(".myelements").texts()) will now automatically requery if a stale element exception occurs. You can disable this behaviour by setting the webdriver.retry.on.stable.element.exception property to false.
  • Improved Playwright/Screenplay integration
  • Support for @​singlebrowser annotation in Cucumber scenarios
  • Bug fixes include:

3.1.20

Minor update including some bug fixes, performance improvements, enhanced Playwright support, and support for Selenium 4.1.2

3.1.15

This release includes support for Selenium 4.1.1 and Cucumber 7, as well as various bug fixes. We have also introduced beta support for Playwright using Screenplay.

3.1.0

Serenity 3.1.0 is a major new release of Serenity BDD. Some of the more significant changes include:

  • Integration with Selenium 4 and Appium 8
  • Improved reporting, including reporting on test duration
  • New responsive report layout
  • Use the serenity.report.accesibility property to render reports using patterns instead of plain colors
  • Filtering Cucumber scenarios (e.g. using the "cucumber.filter.tags" option will now exclude filtered features from appearing in the reports, allowing more focused reporting)
  • Added the WebDriverManagerEnhancer interface, which allows you to write custom code to integrate with the more advanced WebDriverManager features from within Serenity.
  • Chrome is now the default browser
  • Added the SingleBrowser annotation and tag which can be used in JUnit or Cucumber to run all the scenarios in a test suite, feature or scenario outline in a single browser instance
  • Added the InTheBrowser task which makes it easier to perform direct WebDriver operations from within a Screenplay task.

For more details about the new features read this article.

v2.6.0 support for JUnit 5

Serenity 2.6.0 is a major update that adds beta support for JUnit5.

  • In comparison with the JUnit4 integration, for JUnit5 tests no additional annotation is needed. Short overview of supported features/annotations
  • Tagging : @Tag("type:name") - mvn clean verify -Dtags="type:name"
  • Data Driven tests: @ParameterizedTest,@ValueSource,@EnumSource,@CsvFileSource
  • Nested tests: @Nested
  • @DisplayName for methods

The following plugins must be upgraded to the version 3.0.0-M5

  • maven-surefire-plugin
  • maven-failsafe-plugin

A big callout to @​cliviu who spearheaded this module!

... (truncated)

Commits


Updates serenity-rest-assured from 2.3.4 to 3.4.2

Release notes

Sourced from serenity-rest-assured's releases.

3.2.0

Serenity 3.2.0 contains a number of bug fixes and enhancements, including:

  • Improved performance in report generation
  • Updated the Page Elements API (https://serenity-bdd.github.io/documentation/docs/guide/page_elements)
  • Improved requirements reporting to include more comprehensive requirements tables and better support for deep requirements hierarchies
  • Collections of elements retrieved with findAll() methods and then processed (e.g. findAll(".myelements").texts()) will now automatically requery if a stale element exception occurs. You can disable this behaviour by setting the webdriver.retry.on.stable.element.exception property to false.
  • Improved Playwright/Screenplay integration
  • Support for @​singlebrowser annotation in Cucumber scenarios
  • Bug fixes include:

3.1.20

Minor update including some bug fixes, performance improvements, enhanced Playwright support, and support for Selenium 4.1.2

3.1.15

This release includes support for Selenium 4.1.1 and Cucumber 7, as well as various bug fixes. We have also introduced beta support for Playwright using Screenplay.

3.1.0

Serenity 3.1.0 is a major new release of Serenity BDD. Some of the more significant changes include:

  • Integration with Selenium 4 and Appium 8
  • Improved reporting, including reporting on test duration
  • New responsive report layout
  • Use the serenity.report.accesibility property to render reports using patterns instead of plain colors
  • Filtering Cucumber scenarios (e.g. using the "cucumber.filter.tags" option will now exclude filtered features from appearing in the reports, allowing more focused reporting)
  • Added the WebDriverManagerEnhancer interface, which allows you to write custom code to integrate with the more advanced WebDriverManager features from within Serenity.
  • Chrome is now the default browser
  • Added the SingleBrowser annotation and tag which can be used in JUnit or Cucumber to run all the scenarios in a test suite, feature or scenario outline in a single browser instance
  • Added the InTheBrowser task which makes it easier to perform direct WebDriver operations from within a Screenplay task.

For more details about the new features read this article.

v2.6.0 support for JUnit 5

Serenity 2.6.0 is a major update that adds beta support for JUnit5.

  • In comparison with the JUnit4 integration, for JUnit5 tests no additional annotation is needed. Short overview of supported features/annotations
  • Tagging : @Tag("type:name") - mvn clean verify -Dtags="type:name"
  • Data Driven tests: @ParameterizedTest,@ValueSource,@EnumSource,@CsvFileSource
  • Nested tests: @Nested
  • @DisplayName for methods

The following plugins must be upgraded to the version 3.0.0-M5

  • maven-surefire-plugin
  • maven-failsafe-plugin

A big callout to @​cliviu who spearheaded this module!

... (truncated)

Commits


You can trigger a rebase of this PR 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 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)
dependabot[bot] commented 1 year ago

Superseded by #1880.