docs: document test fixture generation
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- dart
- Domain
- documentation, testing
Research direction
Start with test/fixtures/valid_package_info_response.dart and review the linked pull request discussion and pub.dev packages response. Document how the fixture is generated and why it is not a plain snapshot of the response. Done means maintainers can follow the documentation to generate equivalent test fixtures.
Written by the indexing model from the issue text.
Description
Description
As a maintainer I would like to have proper documentation explaining how to generate test fixtures.
Additional context
Test fixtures such as this one are unintuitively not a plain snapshot (as explained here) of the pub.dev packages response.
- Dominant language
- Dart
- Stars
- 56
- Forks
- 6
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bus
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100