Use Case Levels of Test

Every student in school - from elementary to graduate - is familiar with the angst of taking tests, hearing the dreaded line "Times up, put your pencils down ," followed by the that feeling of regret as you think "If only I hadn't spent so much time on that one question " I'd like you to consider that writing tests for software is a bit like taking tests in school. Both are tasks typically done in a finite, allotted amount of time, so it's best to have a strategy for using your time wisely, and knowing what techniques work well (or don't ) on various problem types. Innovation and ways of working smarter often arise from the "cross-pollination" of ideas from multiple disciplines of software engineering. This book presents a four-step strategy to budgeting time and innovative test design based on the idea of use case levels of test combined with high bang for the buck ideas from software testing, Quality Function Deployment (QFD), software reliability's operational profiles, Structured Analysis and Design's C.R.U.D. matrix, and formal methods like model-based specification, Programming in Logic (Prolog) and discrete math for testers. The goal of this "cross-pollination" is to provide you the tester with a strategy such that when you hear "Times up, put your pencils down ," you can relax knowing you have used your time for writing tests for your system or application wisely.