-
Notifications
You must be signed in to change notification settings - Fork 746
Closed
Labels
testA PR that adds to testing - used by Release DrafterA PR that adds to testing - used by Release Drafter
Description
Your checklist for this issue
🚨 Please review the guidelines for contributing to this repository.
- Link to any upstream changes that might be required (for example Jenkins Core pull request)
Feature Request
It looks like we have a lot of test framework functionality for JCasC:
- https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/plugin/src/test/java/io/jenkins/plugins/casc/misc/JenkinsConfiguredWithCodeRule.java and dependencies
- Roundtrip tests from @MRamonLeon : [JENKINS-57761] - Add abstract test for export/configure roundtrip #908
- WiP - JCasC support in the Plugin benchmarking support by @AbhyudayaSharma: [JENKINS-57653] Introduce JMH benchmarks to Jenkins Test Harness jenkins-test-harness#135
Currently it is hard to reuse this code, because it is located within the test suites, so an odd dependency is needed. Also, it makes the downstream plugins to pull in more test dependencies than we really want.
<dependency>
<groupId>io.jenkins</groupId>
<artifactId>configuration-as-code</artifactId>
<version>${configuration-as-code.version}</version>
<classifier>tests</classifier>
<scope>test</scope>
</dependency>
What if we introduce a new configuration-as-code-test-harness component which would ship it in a library?
<dependency>
<groupId>io.jenkins</groupId>
<artifactId>configuration-as-code-test-harness</artifactId>
<version>${configuration-as-code.version}</version>
<scope>test</scope>
</dependency>
darxriggs and runzexia
Metadata
Metadata
Assignees
Labels
testA PR that adds to testing - used by Release DrafterA PR that adds to testing - used by Release Drafter