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

fix(manifests/test): add org.junit.jupiter:junit-jupiter-engine as a test runtime dependency #963

Merged
merged 2 commits into from
Mar 22, 2023

Conversation

dbyron-sf
Copy link
Contributor

so junit5 tests run. Before this PR, 9 tests ran in rosco-manifests, all spock tests. After this PR, 32 tests run.

Before:
image

After:
image

Note that spring-boot-starter-test brings in org.junit.jupiter:junit-jupiter-engine so where that's used, we don't need to declare junit-jupiter-engine explicitly. Note also that rosco-core currently only has spock tests, so although it doesn't use spring-boot-starter-test, it doesn't need org.junit.jupiter:junit-jupiter-engine either.

…intage-engine dependency

as it's not needed at test compile time, and since build.gradle supplies a test runtime dependency as of spinnaker#958
…test runtime dependency

so junit5 tests run.  Before this PR, 9 tests ran in rosco-manifests, all spock tests.
After this PR, 32 tests run.

Note that spring-boot-starter-test brings in org.junit.jupiter:junit-jupiter-engine so
where that's used, we don't need to declare junit-jupiter-engine explicitly.  Note also
that rosco-core currently only has spock tests, so although it doesn't use
spring-boot-starter-test, it doesn't need org.junit.jupiter:junit-jupiter-engine either.
@dbyron-sf dbyron-sf added the ready to merge Approved and ready for merge label Mar 22, 2023
@mergify mergify bot added the auto merged label Mar 22, 2023
@mergify mergify bot merged commit c6d00c6 into spinnaker:master Mar 22, 2023
yugaa22 pushed a commit to OpsMx/rosco-oes that referenced this pull request Jun 26, 2023
…test runtime dependency (spinnaker#963)

* chore(manifests): remove testImplementation org.junit.vintage:junit-vintage-engine dependency

as it's not needed at test compile time, and since build.gradle supplies a test runtime dependency as of spinnaker#958

* fix(manifests/test): add org.junit.jupiter:junit-jupiter-engine as a test runtime dependency

so junit5 tests run.  Before this PR, 9 tests ran in rosco-manifests, all spock tests.
After this PR, 32 tests run.

Note that spring-boot-starter-test brings in org.junit.jupiter:junit-jupiter-engine so
where that's used, we don't need to declare junit-jupiter-engine explicitly.  Note also
that rosco-core currently only has spock tests, so although it doesn't use
spring-boot-starter-test, it doesn't need org.junit.jupiter:junit-jupiter-engine either.
nemesisOsorio pushed a commit to OpsMx/rosco-oes that referenced this pull request Apr 27, 2024
…test runtime dependency (spinnaker#963)

* chore(manifests): remove testImplementation org.junit.vintage:junit-vintage-engine dependency

as it's not needed at test compile time, and since build.gradle supplies a test runtime dependency as of spinnaker#958

* fix(manifests/test): add org.junit.jupiter:junit-jupiter-engine as a test runtime dependency

so junit5 tests run.  Before this PR, 9 tests ran in rosco-manifests, all spock tests.
After this PR, 32 tests run.

Note that spring-boot-starter-test brings in org.junit.jupiter:junit-jupiter-engine so
where that's used, we don't need to declare junit-jupiter-engine explicitly.  Note also
that rosco-core currently only has spock tests, so although it doesn't use
spring-boot-starter-test, it doesn't need org.junit.jupiter:junit-jupiter-engine either.
@dbyron-sf dbyron-sf deleted the manifests-test-cleanup branch October 30, 2024 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto merged ready to merge Approved and ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants