Currently the unit and integration tests are run together and can be identified by:
Unit:**/*Test.javaIntegration:**/*TestIT.java
These should be run separately, as dependencies on databases/message queues etc. are not required for unit testing.
The Jacoco configuration needs updating to merge the reports when running in the pipeline.
Both need to be sent to Sonarqube and CodeCov (with_codecov)
Acceptance Criteria:
Given that I have a unit test (*/Test.java)
When I run ./gradlew test
Then it will run only the unit test
And it will not run the integration test
Given that I have an integration test (*/IT.java)
When I run ./gradlew integrationTest
Then it will run only the integration test
And it will not run the integration test
Given that I have unit and integration tests
When I run ./gradlew test
And I run ./gradlw integrationTest
And I run ./jacocoTestReport
Then a report will be generated containing the results for the unit and integration tests together
Currently the unit and integration tests are run together and can be identified by:
Unit:
**/*Test.java
Integration:**/*TestIT.java
These should be run separately, as dependencies on databases/message queues etc. are not required for unit testing.
The Jacoco configuration needs updating to merge the reports when running in the pipeline.
Both need to be sent to Sonarqube and CodeCov (with_codecov)
Acceptance Criteria:
Given that I have a unit test (*/Test.java) When I run
./gradlew test
Then it will run only the unit test And it will not run the integration testGiven that I have an integration test (*/IT.java) When I run
./gradlew integrationTest
Then it will run only the integration test And it will not run the integration testGiven that I have unit and integration tests When I run
./gradlew test
And I run./gradlw integrationTest
And I run./jacocoTestReport
Then a report will be generated containing the results for the unit and integration tests together