[#12900] Gradle task componentTests should not stop entirely when onl…

…y one task fails (#12963)
TEAMMATES · May 12, 2024 · 1ea04f4 · 1ea04f4
1 parent 34248a0
commit 1ea04f4
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/.github/workflows/component.yml b/.github/workflows/component.yml
@@ -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

diff --git a/.github/workflows/jdk17.yml b/.github/workflows/jdk17.yml
@@ -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
diff --git a/.github/workflows/jdk21.yml b/.github/workflows/jdk21.yml
@@ -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
diff --git a/docs/development.md b/docs/development.md
@@ -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.: