Prerequisites
We have to cover the solution with E2E tests. For that we will use Cucumber (latest version) as BDD engine for preparing and running tests. This will push us for adding a new module that will be 100% dedicated for E2E testing purposes and will be isolated from a main application (service).
On this step no test scenario must be implemented, but environment must be prepared for building scenario and then run them. Hence, Spring Boot application (as Test Engine) must be ready to work in combination with Cucumber. From other hand Cucumber must be ready to read feature, use necessary implemented classes, etc.
Spring configuration and features in Gherkin language (scenarios) will be stored under Gradle test folder.
Once everything is done, we may start implementing test scenario against a respective service, plus extending our CI\CD build with E2E tests execution.
Testing Application will use REST API generated based on Open API Swagger specification. That specification will be generated based on a configuration files (openapi.json) that must be stored with this project. That configuration file will be accessible once REST API on User Profile side implemented.
Prerequisites We have to cover the solution with E2E tests. For that we will use Cucumber (latest version) as BDD engine for preparing and running tests. This will push us for adding a new module that will be 100% dedicated for E2E testing purposes and will be isolated from a main application (service).
On this step no test scenario must be implemented, but environment must be prepared for building scenario and then run them. Hence, Spring Boot application (as Test Engine) must be ready to work in combination with Cucumber. From other hand Cucumber must be ready to read feature, use necessary implemented classes, etc.
Spring configuration and features in Gherkin language (scenarios) will be stored under Gradle test folder. Once everything is done, we may start implementing test scenario against a respective service, plus extending our CI\CD build with E2E tests execution.
Testing Application will use REST API generated based on Open API Swagger specification. That specification will be generated based on a configuration files (openapi.json) that must be stored with this project. That configuration file will be accessible once REST API on User Profile side implemented.
Useful links for motivation and samples: Official cucumber guides SB + Cucumber environment example SB + Cucumber Test configuration 1 SB + Cucumber Test configuration 2 Java + Cucumber environment example Standard reports for Java
So that,
DoD