checkForDeprecations looks for a additional deprecation message
v7.8.5
Ensure that the trait IntegrationTestKitBase has a different cleanup method
To avoid the error: 'The method setup should be public as it implements the corresponding method from interface...'
v7.8.4
make apache.commons api scope
v7.8.3
No release notes provided.
v7.8.2
No release notes provided.
v7.8.1
Spock dependency was in incorrect scope. It is not implementation but api dependency. It would cause compilation failures for consumers.
v7.8.0
Decoupling helper functions for creating tests from Spock Framework. Thank you @dansanduleac
v7.7.0
Add parallel mode option to BaseIntegrationSpec
v7.6.0
Default to not using GradleRunner.forwardOutput() which forwards the output of executed builds to the System.out stream. (This behavior can be enabled again via setting forwardOutput for IntegrationTestKitSpec)
With forwardOutput enabled, each test and its console output print to the System.out stream with the indicator STANDARD_OUT
Using
Gradle 6.0.1
v7.5.0
When you are using Gradle 6 in tests. Dependency generator API will start automatically publishing Gradle metadata. DSL for creating dummy dependencies will allow now specify targetCompatibility for those dummy libraries.
v7.4.0
Update dependency on Spock to bring the most recent version 1.3-groovy-2.4
v7.3.0
Generate maven-metadata.xml for repositories for testing to fully support Gradle 6 which will require them for dynamic version resolution.
Commits
011811f Check for deprecations in output looks for another deprecation message
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in the `.dependabot/config.yml` file in this repo:
- Update frequency
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps nebula-test from 7.2.5 to 7.8.6.
Release notes
Sourced from nebula-test's releases.
Commits
011811f
Check for deprecations in output looks for another deprecation messaged9aa077
Do not use info logging levelc8c7423
Gradle 6.3bb8db07
Merge pull request #124 from nebula-plugins/gradle-6_4-compatibilitye526424
Modify allow different target compatibility test to use maven instead of ivy0e61c84
Gradle 6.2.2488a011
Ensure that the trait IntegrationTestKitBase has a different cleanup method3f530cd
Update build.gradle2f58009
plugin-plugin 14.2.16f2cadf
Gradle 6.2.1Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in the `.dependabot/config.yml` file in this repo: - Update frequency - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)