oxidecomputer / oxidecomputer/maghemite
Consolidate integration test infrastructure
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
Mgd and ddm have separate integration test infrastructure that could benefit from consolidation. Ddm currently pretends it's integration tests are unit tests running within the cargo test framework but I'm not sure if that's where we want to be as things seem a better with mgd's more recent approach of creating testing binaries that are easily built and deployed to lab machines and we don't have to fight test runners that present footguns for running tests with shared system resources and make building deployable test binaries very awkward.
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
Compare mgd's newer integration-test approach with ddm's tests running through the cargo test framework; start by locating both infrastructure paths and their test entry points. Define the consolidation scope and verify that the resulting tests can be built and deployed as binaries to lab machines without relying on test-runner behavior for shared system resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100