Automated code coverage measurement and tracking per user story and requirement

摘要

Embodiments of the invention relate to automated code coverage measurement and tracking per user story and requirement. An aspect of the invention includes receiving one or more software development requirements. One or more tasks are generated from the one or more software development requirements. A task identifier (ID) is assigned to each of the one or more tasks, and each of the task IDs is assigned to at least one code component. An application is released that includes at least one code components.

主权项

1. A system having a processor, comprising:
a code coverage module circuit, the code coverage module circuit configured to perform a method comprising:
receiving one or more software development requirements and partitioning the one or more software development requirements into one or more user stories;generating one or more tasks from the one or more user stories;assigning a task identifier (ID) to each of the one or more tasks and mapping each task identifier to one of the one or more user stories from which the task was generated;associating at least one code component with each of the task IDs, the at least one code component comprising software code corresponding to the one or more software development requirements;executing at least one test run, the at least one test run performed by at least one of a code coverage tool and a code testing tool against the at least one code component;producing at least one test result, the at least one test result comprising the test results of the at least one code component executed by the at least one test run;associating the at least one test result with the one or more software development requirements, wherein the at least one test result is associated with the at least one software development requirement by using the task ID of the at least one code component executed by the at least one test run; andgenerating a report that identifies all tasks that have been executed during the at least one test run and includes an indication if any of the tasks failed during their execution, the report further including an amount of code executed during the at least one test run and a breakdown of the amount of code tested successfully and unsuccessfully.