microsoft / microsoft/ApplicationInspector
Improve Automated Testability of Analyze Command
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 366
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 3
Description
AnalyzeCommand should be refactored to at allow mocking calls to RecursiveExtractor, this is currently a bit complicated because of the nested method calls. Alternately, to allow for such capability in other components, this interface should be defined in the RecursiveExtractor library (where it may also be useful for improving the unit tests there). See #599.
Contributor guide
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 with AnalyzeCommand and the RecursiveExtractor library, focusing on how the nested method calls currently prevent mocking. Read issue #599 and the existing unit tests mentioned in the issue; the refactor is done when RecursiveExtractor calls can be mocked and the affected tests can exercise AnalyzeCommand more directly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100