1. PROCESS IMPROVEMENT PROJECT
IMPLEMENT THE USE OF CODE COVERAGE TOOLS FOR TESTING
Mallika Sanyal By

2. AGENDA
The proposal What do code coverage tools do? Current system and its shortfalls Impact of the proposal on project process Analysis of code coverage tools Limitations

3. PROPOSAL
Implement code coverage tools for testing development code. More applicable to architected agile projects.

4. WHAT DO CODE COVERAGE TOOLS DO?
Checks whether the entire code has been covered in the tests conducted. Identify redundant test cases. Identify chunks of code not tested. Improve quality of code

5. CURRENT SYSTEM Tester submits Test plan and cases
Regression test package
Acceptance test plan
Unit testing

6. SHORTFALLS OF CURRENT SYSTEM
No way to identify whether parts of code have deliberately been left out, indicating unethical prototyping. No way to find out if the entire code has been tested. No way to find out if the failure of conditions have been tested. No way to pinpoint the location of a bug, thereby reducing debugging effort.

7. FEASIBLITY If used in moderation, feasible. Divide code into
High Risk (Core capabilities, integration code)
Medium Risk (major conditional statements, error handling)
Low Risk (general UI issues)
Apply code coverage tools accordingly
A lot depends on experience
Screenshots as record.

8. LIMITATIONS
Might not be too useful for NDI/NCS and NDI Intensive projects. If not executed properly, might become an overkill. There are ways to work around a coverage tool. What about commented code? Cannot pinpoint error in logic

9. References
tId=

10. THANK YOU