Page - 4 - in The Future of Software Quality Assurance

4 S. Amann and E. Jürgens Fig. 2 Treemaps that show data about thesoftware systemTeamscale from theversion-control system, the ticket system, and profiling test execution. (a) Source code as a Treemap. Each box represents one method. The size of the box is proportional to the lines of code in that method. (b) Code changes since a fixed baseline. New methods are red, changed methods are yellow, and methods that remain unchanged are gray. (c) Code changes for ticketTS-15717. New methods are red and changed methods are yellow. (d) Test coverage on method-level. Methods that have been executed are green, all other methods are gray red,methods that werechangedarehighlighted in yellow,andmethods that remain unchangedarehighlighted in gray. 2.2 Ticket Systems Ticket systems, such as Jira or GitHub Issues, are used in most software projects to keep track of change requests, such as bug reports, feature requests, or maintenance tasks. Such systems allow the development team to manage each request asa ticket,whichusuallyhasa uniqueID,an assignee, anda status, among othermetadata. It is a widely used practice that developers annotate changes in the version- control system with the ID of the ticket(s) that motivated the changes, usually by adding the ID to the commit message that describes the respective change. Using these annotationsof the code changesand the metadata from the ticket system, we