Page - 11 - in The Future of Software Quality Assurance

Change-Driven Testing 11 0 5 10 15 20 25 30 35 40 45 50 CI with TIA Regular CI Time [min] Build Test Execution Fixing the Bug Fig. 7 The gain from using test-impact analysis. Two consecutive CI runs using TIA plus correcting a mistake take less time than one CI run withTeamscale’s full test suite Fig. 8 Ticket coverage forTS-15717 after executing the impacted tests identifiedby TIA. TGA reveals one remaining testgap were tested (thegreenrectangles),butone test gapremains(the redrectangle in the lower right). To decide whether the remaining test gap is worth closing, our developer drills down from the treemap into the code. She discovers that the untested code is responsibleforrequestinganadditionalconfirmation,whenauserattemptstodelete credentials that are still used byTeamscale. Since this code is relatively simple andunlikely toeverchange, shedecides to test it oncemanually. Our developer starts the development version of Teamscale from her local machine, using a manual-test startup script that we maintain with our code. She opensthesystemundertest inabrowser,navigatesto theadministrativeperspective, andcheckswhether theadditionalconfirmationis indeedrequested. It is, andsoshe shuts down the system under test, which causes the startup script to automatically provide the recorded coverage for TGA. As a result, all changes forTS-15717 werenowtested,verifiablydocumentedbyanall-green test-gap treemap.