microsoft / microsoft/RecursiveExtractor
Improve tests to validate the correct contents of extracted files
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 220
- Forks
- 35
- Avg merge
- 20d 1h
- Merged PRs (30d)
- 1
Description
Currently the tests primarily check that the correct number of files are returned from extraction commands. However, as the issue identified in #102 shows this can be insufficient in cases where the underlying library may not be threadsafe (for example). In such cases the tests can still succeed, finding the correct number of files, but their contents may be incomplete. We should develop additional tests that verify for each file type we support that the contents + sizes of each file are correct. Perhaps the easiest method would be with a hash of the contents of the extracted stream.
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 locating the existing tests for extraction commands and review issue #102 for the failure scenario. Extend coverage across each supported file type so tests verify extracted file contents and sizes, potentially by hashing each extracted stream. Done means the tests catch incomplete contents even when the expected file count is returned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100