ci: add JUnit sample test workflow#7
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a GitHub Actions workflow that runs the
junit-sampleintegration test againstimposter-jvm-engine'smain, mirroring the check that lives in the engine repo today.Summary
.github/workflows/junit-sample.yaml: checks out this repo andimposter-project/imposter-jvm-engine, publishes the engine to a local Maven repo (./gradlew publishToMavenLocal -xtest), then runs./mvnw testagainst the locally-published SNAPSHOTmain, pull requests, and manualworkflow_dispatchEnricoMi/publish-unit-test-result-actionso failures surface as checksImplementation details
Mirrors the existing
Examplesjob inimposter-jvm-engine. Having the check here lets contributions to the examples repo block on the same combination before merge — previously a breaking change to a sample pom (like the Jackson version drift fixed in #5) would only surface on the engine's next CI run.