Add tests with hard-coded input and expectations
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6
- Forks
- 6
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 4
Description
Go through all the tests that generate data and expectations, and extract the interesting cases into granular tests with fixed input and fixed expectations.
Once the format stabilizes, soon hopefully, this will be less become very valuable IMHO, and also be more practical to implement since there won't be churn that requires changing all the fixed tests.
See also https://github.com/microsoft/security-utilities/issues/147 for rationale.
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 inventorying the C# tests that generate data and expectations, then read the rationale in security-utilities issue 147. Identify stable, interesting cases and confirm the format before extracting granular tests with fixed inputs and fixed expectations. Done means the relevant generated cases are covered without depending on generated expectations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100