Merge pull request #27 from eliasnogueira/general-updates

General updates

.mvn/wrapper/maven-wrapper.properties

@@ -14,5 +14,6 @@
 # KIND, either express or implied.  See the License for the
 # specific language governing permissions and limitations
 # under the License.
-distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip
-wrapperUrl=https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.2.0/maven-wrapper-3.2.0.jar
+wrapperVersion=3.3.2
+distributionType=only-script
+distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.7/apache-maven-3.9.7-bin.zip

CHANGELOG.md

@@ -4,9 +4,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.4.1] - 26-05-2024
+- Bump `actions/cache`
+- Bump Maven Wrapper
+- Change message e-mail expected error message in the `SimulationErrorsData`
+- Updated the following dependencies
+  - `junit.jupiter.version -> 5.11.0-M2`
+  - `assertj.version -> 3.26.0`
+  - `datafaker.version -> 2.2.2`
+  - `slf4j.version -> 2.0.13`
+  - `allure.version -> 2.27.0`
+  - `aspectj.version -> 1.9.22.1`
+
 ## [2.4.0] - 20-03-2024
 
-## Changed
+### Changed
 
 - Adopt Java 22
   - Set `java.version` to 22
@@ -27,7 +39,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [2.3.1] - 17-12-2023
 
-## Changed
+### Changed
 - Updated the following dependencies
   - `maven-surefire-plugin -> 3.2.3`
   - `restassured -> 5.4.0`
@@ -37,7 +49,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [2.3.0] - 06-11-2023
 
-## Changed
+### Changed
 - Set Java version as 21 in the `pom.xml` and `.github/workflows/test-execution.yml`
 - Updated Maven Wrapper
 - Updated the following dependencies
@@ -50,25 +62,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - `allure.version -> 2.24.0`
   - `aspectj.version -> 1.9.20.1`
 
-## Removed
+### Removed
 - Removed custom BaseTest classes for Restrictions and Simulations as the data factories shouldn't be instantiated
 
 ## [2.2.6] - 06-06-2023
 
-## Changed
+### Changed
 - Update the following dependencies
-  - maven-surefire-plugin.version>3.1.2
-  - restassured.version>5.3.1
-  - junit.jupiter.version>5.10.0-M1
-  - datafaker.version>2.0.1
-  - allure.version>2.23.0
-  - aspectj.version>1.9.19
+  - `maven-surefire-plugin.version -> 3.1.2`
+  - `restassured.version -> 5.3.1`
+  - `junit.jupiter.version -> 5.10.0-M1`
+  - `datafaker.version -> 2.0.1`
+  - `allure.version -> 2.23.0`
+  - `aspectj.version -> 1.9.19`
 - Added `commons-codec` and `jackson-databind` libraries explicitly to solve dependencies security issues
 - Updated `READM` and `CONTRIBUTION` mentioning Java 17
 
 ## [2.2.5] - 14-03-2023
 
-## Changed
+### Changed
 - Update the following dependencies
  - `allure-maven -> 2.12.0`
  - `allure -> 2.21.0`
@@ -86,7 +98,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [2.2.4] - 27-09-2022
 
-## Changed
+### Changed
 - Adoption of Java 17
 - Replace of JavaFaker by DataFaker at
   - `RestricitonDataFactory`
@@ -108,7 +120,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - `allure-2.19.0`
   - `aspectj-1.9.9.1`
 
-## Removed
+### Removed
 - Removed `CpfGenerator` and replaced by the DataFaker `faker.cpf().valid()`
 
 ## [2.2.3] - 03-07-2022

README.md

@@ -45,24 +45,24 @@ Please, before executing any tests, run the backend API.
 After cloning this project:
 
 1. Navigate to the project folder using the Terminal / Command prompt
-2. Execute the following: `mvn spring-boot:run`
+2. Execute the following: `./mvnw spring-boot:run`
 3. Wait until you see something like this: _Application has started! Happy tests!_
 4. The API is ready and listen to all requests on `http://localhost:8088`
 
 ### Running the test suites
 
 The test suites can be run directly by your IDE or by command line.
-If you run `mvn test` all the tests will execute because it's the regular Maven lifecycle to run all the tests.
+If you run `./mvnw test` all the tests will execute because it's the regular Maven lifecycle to run all the tests.
 
 To run different suites based on the groups defined for each test you must inform the property `-Dgroups` and the group names.
 The example below shows how to run the test for each pipeline stage:
 
-| pipeline stage     | command                          |
-|--------------------|----------------------------------|
-| health check tests | `mvn test -Dgroups="health"`     |
-| contract tests     | `mvn test -Dgroups="contract"`   |
-| functional tests   | `mvn test -Dgroups="functional"` |
-| e2e tests          | `mvn test -Dgroups="e2e"`        |
+| pipeline stage     | command                             |
+|--------------------|-------------------------------------|
+| health check tests | `./mvnw test -Dgroups="health"`     |
+| contract tests     | `./mvnw test -Dgroups="contract"`   |
+| functional tests   | `./mvnw test -Dgroups="functional"` |
+| e2e tests          | `./mvnw test -Dgroups="e2e"`        |
 
 ### Generating the test report
 
@@ -72,8 +72,8 @@ There are some configuration to make it happen:
 * `allure.properties` file on `src/test/resources`
 
 You can use the command line to generate it in two ways:
-* `mvn allure:serve`: will open the HTML report into the browser
-* `mvn allure:report`: will generate the HTML port at `target/site/allure-maven-plugin` folder
+* `./mvnw allure:serve`: will open the HTML report into the browser
+* `./mvnw allure:report`: will generate the HTML port at `target/site/allure-maven-plugin` folder
 
 ## About the Project Structure