Ensure that test invocations are targeted at a specific use-case

- Remove the 'gradle --stop' step from the prod workflow.
  We either need to stop all instances started, or rely on GitHub to clean up processes on completion.
- Remove configuration-cache and dependencies-cache from basic tests. We will later need to add
  tests invocations specific for these features.
This commit is contained in:
Daz DeBoer 2021-06-09 11:48:43 -06:00
parent 18c8a679dc
commit 643092d2fc

View File

@ -14,34 +14,20 @@ jobs:
steps:
- name: Checkout sources
uses: actions/checkout@v2
- name: Test wrapper
- name: Test use Gradle wrapper
uses: ./
with:
build-root-directory: __tests__/data/basic
dependencies-cache-enabled: true
configuration-cache-enabled: true
arguments: test
- name: Test custom wrapper location
uses: ./
with:
build-root-directory: __tests__/data/basic
wrapper-directory: __tests__/data/basic
dependencies-cache-enabled: false
configuration-cache-enabled: false
arguments: test
- name: Test dist download
- name: Test use defined Gradle version
uses: ./
with:
gradle-version: rc
build-root-directory: __tests__/data/basic
dependencies-cache-enabled: true
configuration-cache-enabled: true
arguments: test --configuration-cache
- name: Stop Gradle daemon
uses: ./
with:
gradle-version: rc
build-root-directory: __tests__/data/basic
dependencies-cache-enabled: true
configuration-cache-enabled: true
arguments: --stop
arguments: test