Show simple item record

dc.contributor.advisorStålhane, Tornb_NO
dc.contributor.advisorRynning, Ole Christiannb_NO
dc.contributor.authorDalatun, Sveinungnb_NO
dc.contributor.authorRemøy, Simon Ingenb_NO
dc.contributor.authorSeth, Thor Kristian Ravnangernb_NO
dc.contributor.authorVoldsund, Øyvindnb_NO
dc.date.accessioned2014-12-19T13:37:43Z
dc.date.available2014-12-19T13:37:43Z
dc.date.created2011-10-03nb_NO
dc.date.issued2011nb_NO
dc.identifier445175nb_NO
dc.identifierntnudaim:5862nb_NO
dc.identifier.urihttp://hdl.handle.net/11250/252597
dc.description.abstractRunning automated tests can be a time-consuming task, especially when doing regression testing. If the sequence of the execution of the test cases is arbitrary, there is a good chance that many of the defects are not detected until the end of the test run. If the developer could get the failing tests first, he would almost immediately be able to get back to coding or correcting mistakes. In order to achieve this, we designed and analyzed a set of test case prioritization techniques. The prioritization techniques were compared in an experiment, and evaluated against two existing techniques for prioritizing test cases.Our implementation of the prioritization techniques resulted in a tool called Pritest, built according to good design principles for performance, adaptability and maintainability. This tool was compared to an existing similar tool through a discussion.The problem we address is relevant for the increased popularity of agile software methods, where rapid regression testing is of high importance. The experiment indicates that some prioritization techniques perform better than others, and that techniques based on code analysis is outperformed by techniques analyzing code changes, in the context of our experiment.nb_NO
dc.languageengnb_NO
dc.publisherInstitutt for datateknikk og informasjonsvitenskapnb_NO
dc.subjectntnudaim:5862no_NO
dc.subjectMTDT datateknikkno_NO
dc.subjectProgram- og informasjonssystemerno_NO
dc.subjectDatateknikkno_NO
dc.titleDecreasing Response Time of Failing Automated Tests by Applying Test Case Prioritizationnb_NO
dc.typeMaster thesisnb_NO
dc.source.pagenumber198nb_NO
dc.contributor.departmentNorges teknisk-naturvitenskapelige universitet, Fakultet for informasjonsteknologi, matematikk og elektroteknikk, Institutt for datateknikk og informasjonsvitenskapnb_NO


Files in this item

Thumbnail
Thumbnail

This item appears in the following Collection(s)

Show simple item record