Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#12900] Gradle task componentTests should not stop entirely when only one task fails #12963

Merged
merged 8 commits into from
May 12, 2024
2 changes: 1 addition & 1 deletion .github/workflows/component.yml
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ jobs:
run: docker-compose run -d -p 8983:8983 solr
- name: Run Backend Tests
run: |
./gradlew createConfigs componentTests
./gradlew createConfigs componentTests --continue
./gradlew jacocoReport
- name: Generate Types
run: ./gradlew generateTypes
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/jdk17.yml
Original file line number Diff line number Diff line change
Expand Up @@ -31,4 +31,4 @@ jobs:
- name: Run Solr search service
run: docker-compose run -d -p 8983:8983 solr
- name: Run Backend Tests
run: ./gradlew createConfigs componentTests
run: ./gradlew createConfigs componentTests --continue
2 changes: 1 addition & 1 deletion docs/development.md
Original file line number Diff line number Diff line change
Expand Up @@ -326,7 +326,7 @@ Back-end component tests follow this configuration:

Test suite | Command | Results can be viewed in
---|---|---
`Component tests` | `./gradlew componentTests` | `{project folder}/build/reports/tests/componentTests/index.html`
`Component tests` | `./gradlew componentTests --continue` | `{project folder}/build/reports/tests/componentTests/index.html`
Any individual component test | `./gradlew componentTests --tests TestClassName` | `{project folder}/build/reports/tests/componentTests/index.html`

You can generate the coverage data with `jacocoReport` task after running tests, e.g.:
Expand Down