Insight or Just Numbers?
To paraphrase Lord Kelvin, a test team has little insight if they have no metrics. However, there are plenty of test teams who, through the wrong choice or improper use of metrics, have plenty of metrics, but no insight. To learn more about common metrics mistakes, click here to listen to my keynote speech at PNSQC earlier this month.
Ich unterstütze agile Softwareteams, den Karren aus dem Sumpf schlechter Qualit?t zu ziehen.
8 å¹´Even if testcases aren't linked to requirements I - as a test manager - want to know how "good" the testcases are. If a major percentage of test cases written doesn't detect important defects, I need to analyse that. Is the quality of the system under test that good? Really? Or are we doing just the wrong things? Besides that I am an advocate of reviews - you surely know this - and if done correctly they really give superb measurements for improvement :-)
Senior SQA manager, Expert en amélioration des processus de test, Auteur
8 å¹´Same issue with measuring test cases (passed, failed etc.) when there is no link between test cases and requirements. Who cares about test cases? Customers care about functionalities and cost, developers care about defects and code quality, hierarchy cares about cost and time to market (or delivery of the software). So why persist in measuring test cases? Why not measure 'fulfilled requirements' or 'covered quality characteristics', etc.? What about prevented defects, measured through reviews? (Who does reviews, really?). Measurements cost, and only provide you with answers to questions, if you know what questions to ask (and which questions are important). Best regards