softwaremill / softwaremill/chimp
T3 - conformance tests infrastructure for two revisions
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 102
- Forks
- 10
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 16
Description
Target branch: 2026-07-28-protocol-support
Run 4 conformance steps o CI: client and server, at 2025-11-25 and at 2026-07-28. Rename conformance-baseline.yml to conformance-baseline-2025-11-25.yml, add conformance-baseline-2026-07-28.yml with every scored 2026-07-28 scenario (37 server, 32 client). The sbt conformance task selects the baseline file from the --requirements argument. Update both conformance READMEs with the two-revision commands and the single scenario form --scenario X --spec-version 2026-07-28. The harness version stays at 0.2.0-alpha.11.
Spec:
Conformance scenarios that must pass after this task: none new.
Docs: no.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting conformance-baseline.yml, the sbt conformance task, and both conformance READMEs. Trace how --requirements selects a baseline, then update the two revision files and commands so the four CI conformance steps use the requested requirement sets and all listed scenarios pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100