{"id":{"repo_id":"usf","oai_identifier":"oai:digitalcommons.usf.edu:etd-3937"},"canonical_url":"https://search.ndltd.org/etd/usf/oai:digitalcommons.usf.edu:etd-3937","repository":{"repo_id":"usf","name":"University of South Florida","base_url":"https://digitalcommons.usf.edu/do/oai/"},"display":{"title":"Understanding ROI Metrics for Software Test Automation","abstract":"Software test automation is widely accepted as an efficient software testing technique. However, automation has failed to deliver the expected productivity more often than not. The goal of this research was to find out the reason for these failures by collecting and understanding the metrics that affect software test automation and provide recommendations on how to successfully adopt automation with a positive return on investment (ROI). The metrics of concern were schedule, cost and effectiveness. The research employed an experimental study where subjects worked on individual manual and automated testing projects. The data collected were cross verified and supplemented with additional data from a feedback survey at the end of the experiment. The results of this study suggest that automation involves a heavy initial investment in terms of schedule and cost, which needs to be amortized over subsequent test cycles or even subsequent test projects. A positive ROI takes time and any decision to automate should take into consideration the profit margin per cycle and the number of cycles required to break even. In this regard, automation has been found to be effective for testing that is highly repetitive in nature like, smoke testing, regression testing, load testing and stress testing.","abstract_html":"Software test automation is widely accepted as an efficient software testing technique. However, automation has failed to deliver the expected productivity more often than not. The goal of this research was to find out the reason for these failures by collecting and understanding the metrics that affect software test automation and provide recommendations on how to successfully adopt automation with a positive return on investment (ROI). The metrics of concern were schedule, cost and effectiveness. The research employed an experimental study where subjects worked on individual manual and automated testing projects. The data collected were cross verified and supplemented with additional data from a feedback survey at the end of the experiment. The results of this study suggest that automation involves a heavy initial investment in terms of schedule and cost, which needs to be amortized over subsequent test cycles or even subsequent test projects. A positive ROI takes time and any decision to automate should take into consideration the profit margin per cycle and the number of cycles required to break even. In this regard, automation has been found to be effective for testing that is highly repetitive in nature like, smoke testing, regression testing, load testing and stress testing.","abstract_has_math":false,"creators":["Jayachandran, Naveen"],"institution":"University of South Florida","degree_name":null,"degree_level":"Thesis","degree_discipline":"Computer Science","degree_department":null,"school":null,"contributors":["Dewey Rundus, Ph.D.","Alan Hevner, Ph.D.","Rafael Perez, Ph.D."],"advisors":[],"committee_chairs":[],"committee_members":[],"year":2005,"date_issued":"2005-01-01T08:00:00Z","date_published":"2005-01-01T08:00:00Z","updated_at":"2026-11-19T08:35:14Z","subjects":["Return on investment metrics","Automated testing feasibility","Manual vs. automated testing","Software quality assurance","Regression testing","Repetitive testing","American Studies","Arts and Humanities"],"languages":["EN-US"],"rights":[],"rights_urls":[],"identifier_entries":[],"person_identifier_entries":[]},"links":{"outbound_url":"https://digitalcommons.usf.edu/etd/2938","outbound_label":"Repository record","outbound_source":"dc:identifier","record_url":"https://digitalcommons.usf.edu/etd/2938","record_label":"Repository record","record_kind":"record","record_source":"dc:identifier","download_url":null,"download_label":null,"download_source":null,"access_status":null,"embargo_until":null,"access_note":null},"source_record":{"url":"https://digitalcommons.usf.edu/do/oai/?verb=GetRecord&metadataPrefix=oai_etdms&identifier=oai%3Adigitalcommons.usf.edu%3Aetd-3937","prefix":"oai_etdms"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor","label":"Contributor","values":["Dewey Rundus, Ph.D.","Alan Hevner, Ph.D.","Rafael Perez, Ph.D."]},{"key":"dc:creator","label":"Author","values":["Jayachandran, Naveen"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date","label":"Dc Date","values":["2005-01-01T08:00:00Z"]},{"key":"thesis:degree_discipline","label":"Discipline","values":["Computer Science"]},{"key":"thesis:degree_level","label":"Degree Level","values":["Thesis","M.S.C.S."]},{"key":"thesis:institution_name","label":"Thesis Institution Name","values":["University of South Florida"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["Return on investment metrics","Automated testing feasibility","Manual vs. automated testing","Software quality assurance","Regression testing","Repetitive testing","American Studies","Arts and Humanities"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language","label":"Dc Language","values":["EN-US"]},{"key":"dc:rights.license","label":"Dc Rights License","values":["default"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["https://digitalcommons.usf.edu/etd/2938"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description","label":"Description","values":["Software test automation is widely accepted as an efficient software testing technique. However, automation has failed to deliver the expected productivity more often than not. The goal of this research was to find out the reason for these failures by collecting and understanding the metrics that affect software test automation and provide recommendations on how to successfully adopt automation with a positive return on investment (ROI). The metrics of concern were schedule, cost and effectiveness. The research employed an experimental study where subjects worked on individual manual and automated testing projects. The data collected were cross verified and supplemented with additional data from a feedback survey at the end of the experiment. The results of this study suggest that automation involves a heavy initial investment in terms of schedule and cost, which needs to be amortized over subsequent test cycles or even subsequent test projects. A positive ROI takes time and any decision to automate should take into consideration the profit margin per cycle and the number of cycles required to break even. In this regard, automation has been found to be effective for testing that is highly repetitive in nature like, smoke testing, regression testing, load testing and stress testing."]},{"key":"dc:title","label":"Title","values":["Understanding ROI Metrics for Software Test Automation"]}]}],"canonical_facts":{"dc:contributor":["Dewey Rundus, Ph.D.","Alan Hevner, Ph.D.","Rafael Perez, Ph.D."],"dc:creator":["Jayachandran, Naveen"],"dc:date":["2005-01-01T08:00:00Z"],"dc:description":["Software test automation is widely accepted as an efficient software testing technique. However, automation has failed to deliver the expected productivity more often than not. The goal of this research was to find out the reason for these failures by collecting and understanding the metrics that affect software test automation and provide recommendations on how to successfully adopt automation with a positive return on investment (ROI). The metrics of concern were schedule, cost and effectiveness. The research employed an experimental study where subjects worked on individual manual and automated testing projects. The data collected were cross verified and supplemented with additional data from a feedback survey at the end of the experiment. The results of this study suggest that automation involves a heavy initial investment in terms of schedule and cost, which needs to be amortized over subsequent test cycles or even subsequent test projects. A positive ROI takes time and any decision to automate should take into consideration the profit margin per cycle and the number of cycles required to break even. In this regard, automation has been found to be effective for testing that is highly repetitive in nature like, smoke testing, regression testing, load testing and stress testing."],"dc:identifier":["https://digitalcommons.usf.edu/etd/2938"],"dc:language":["EN-US"],"dc:rights.license":["default"],"dc:subject":["Return on investment metrics","Automated testing feasibility","Manual vs. automated testing","Software quality assurance","Regression testing","Repetitive testing","American Studies","Arts and Humanities"],"dc:title":["Understanding ROI Metrics for Software Test Automation"],"thesis:degree_discipline":["Computer Science"],"thesis:degree_level":["Thesis","M.S.C.S."],"thesis:institution_name":["University of South Florida"]},"updated_at":"2026-11-19T08:35:14Z"}