Branch coverage
Registered by
Michal Kwiatkowski
Extend static analysis with control flow graph analysis capabilities to come up with sets of inputs that cover each possible branch of execution. Combine this with dynamic analysis of calls with those inputs to come up with real test cases that improve branch coverage of the code.
Because the code has to be run before we can generate a test case, do this only for safe functions (e.g. functions without side effects or with side effects we can handle).
Since we'll be testing a lot of input values, but are only interested in the outcome, calls should be grouped into equivalence classes.
Blueprint information
- Status:
- Not started
- Approver:
- Michal Kwiatkowski
- Priority:
- Medium
- Drafter:
- Michal Kwiatkowski
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- 0.7-fuzzy-testing
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.