oxidecomputer / oxidecomputer/propolis
PHD: support parameterized test cases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
Some test cases lend themselves very well to parameterization: if I launch an instance with X CPUs and Y CPU topology, then I expect the guest to see X and Y represented in such-and-such a way in the output from such-and-such commands, for a range of values of X and Y. There are some parameterized testing crates in the broader ecosystem, but I'm not sure any of them are applicable to freestanding test runners like PHD, so we might have to roll our own parameterization mechanism here, e.g. as an extension to the #[phd_testcase] macro.
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 reading the PHD freestanding test runner and the #[phd_testcase] macro. Determine how parameterized cases should represent CPU counts and topology across the broader ecosystem, then define what a completed mechanism must demonstrate for guest-visible command output over multiple X and Y values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100