Test cases beyond what's in the software requirements specification

More information on software test cases How to design test cases How to design test cases from use cases Granularity in test case design

The most important document to refer to while writing test cases is the software requirements specification (SRS). Mostly, testers stop writing new test cases when they have covered everything in the SRS, but you can come up with even more new test cases once the development team starts giving you a working build.

Once a build is given to the test team for testing, the testers will find bugs in the build. Now, you can refer each bug that was found and can analyze whether a test case can be written to incorporate this scenario or not. And you will mostly find few scenarios that were actually not written in the initial phase and that can be a good test case. The tester when doing an ad hoc testing can come across some out-of-the-box steps that can reveal some bugs. So, it always better to keep on analyzing the bugs that were filed and update the test case document regularly.

Rate this Tip To rate tips, you must be a member of SearchSoftwareQuality.com. Register now to start rating these tips. Log in if you are already a member. Submit a Tip Digg This!     StumbleUpon     Del.icio.us    RELATED CONTENT Software Testing What to include in a performance test plan Unit testing in the enterprise: Five common myths dispelled Determining the testing organization's place within a company How to test a data warehouse Testing for performance, part 3: Provide information The effectiveness of code coverage tools in software testing Use HAST to determine the robustness of a system Increasing tester interactions with developers Testing for performance, part 2: Build out the test assets Testing for performance, part 1: Assess the problem space Software testing and quality assurance (QA) fundamentals Testing software in the dark is problematic Software testers: Identity crisis or delusions of grandeur? Determining the testing organization's place within a company How to test a data warehouse Software testing fundamentals: Testing basics Software testing fundamentals: Other useful resources Software requirements sign-off essential for solid QA How to specialize in performance testing The effectiveness of code coverage tools in software testing How to thoroughly test a website without automated tools RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary build  (SearchSoftwareQuality.com) code review  (SearchSoftwareQuality.com) conformance testing  (SearchSoftwareQuality.com) error handling  (SearchSoftwareQuality.com) garbage in, garbage out  (SearchSoftwareQuality.com) load testing  (SearchSoftwareQuality.com) NUnit  (SearchSoftwareQuality.com) quality assurance  (SearchSoftwareQuality.com) stress testing  (SearchSoftwareQuality.com) white box  (SearchSoftwareQuality.com) RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.