[Code Coverage] Investigate improving code coverage's detection of __salt__
Open
Nobody has claimed this yet.
Tests
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Currently code coverage is not completely accurate due to our usage of __salt__. It does not know how to map __salt__['function'] to the correct function. This issue is to investigate a solution for coverage to accurately detect the code coverage even with the use of __salt__
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 by examining how code coverage handles Python references such as salt['function']; the issue does not name a file, test, or coverage entry point. Trace the coverage mapping for these references and identify a reproducible case, then define completion as accurate coverage detection for salt calls with tests demonstrating the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100