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

Update Maven Integration Tests to use JVM Test Suites #3581

Draft
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

adam-enko
Copy link
Contributor

@adam-enko adam-enko commented Apr 23, 2024

- Migrate the CLI integration tests away from the custom integration test convention (which are not build-cache compatible) to use JVM Test Suites.
- Remove shadowing, replace with passing in the JARs via system properties. (a custom CommandLineArgumentProvider is confusing and overly complicated, but it's required to satisfy Gradle input normalization, so that the build-cache can be re-used.)
- Simplify `processUtils.kt` - the coroutines logic isn't necessary since the entrypoint just used `runBlocking {}`.
- move `jsonBuilder.kt` test-util into `src/main`, since it's not a test
- Rename `CliIntegrationTest` to `CliTest` (it wasn't an integration test, and the name was confusing compared to the actual `CliIntegrationTest`)
@adam-enko adam-enko force-pushed the KT-64200/maven-jvm-test-suite branch from 8b6dba6 to 16278e0 Compare April 24, 2024 12:50
@adam-enko adam-enko changed the title Update CLI Integration Tests to use JVM Test Suites Update Maven Integration Tests to use JVM Test Suites Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant