When to begin testing in the SDLC

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Testing and Quality Assurance What are the top free and not-free automated test tools? Test case preparation for a Web-based application The difference between functional testing and regression testing Free load/performance testing tools for Java-based Web applications Mapping results in test environment to production environment What are some debugging shortcuts to reduce frequent debugging? How to get a software testing job in a recession How to write a test strategy document What are the risks in using open source test automation tools? What is system integration testing? Advice from Mike Kelly Integration testing: Is it black box or white box testing? Test strategy document vs. an acceptance test plan The future of software testing An approach to integration testing Choosing code coverage tools Performance testing and experimental design How to test software with dynamic requirements Test metrics and use case coverage during testing How to learn white box testing How to determine test coverage Software testing and quality assurance (QA) fundamentals Five roles test managers play in agile development: Tutorial, part one Three software regression testing steps can perfect defect fixes Software Testing: Assessing risk and scope Software Testing: How to know you're ready to start testing Quality assurance (QA) and testing's role in requirements Test case preparation for a Web-based application The difference between functional testing and regression testing Mapping results in test environment to production environment Agile software development tutorial: Agile testing Creating strong QA and testing strategies in a changing world

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

This is a difficult question to answer because it really depends on your context: the business users, the development team, and what style of development you're doing. There isn't one development lifecycle that works for all companies, or even all teams within a company. Each context is unique, and what works at one company may fail at another because of small -- possibly initially undetectable -- differences.

For example, if you're working in an agile environment, then I think the answer would be to get the application in front of testing and the business as soon as you get something working. Even if there might be some issues, the early and rapid feedback is important. If you're working in a more contact-heavy environment, and there are political or contractual ramifications to the business users finding issues, then you might want to wait until testing has covered the significant risks and areas of the product.

In your context, if you wanted to release the application to testing and business users earlier, you might want to answer the following questions:

• Do we have a method for capturing early feedback from testers and users? This may or may not be your normal testing processes and tools.



• How will the development team (that's not only the programmers, but other testers, project managers, analysts, and other stakeholders) respond to early feedback if they get it?



• How will the testers respond to getting application earlier, perhaps in a less stable state? Will it make their jobs easier or more difficult? What would that team need to change to support that new process?



• How will the business users respond to getting application earlier, perhaps in a less stable state? Will it make their jobs easier or more difficult? What would that team need to change to support that new process?



• Are there any metrics that we currently capture that we may need to re-evaluate if we change when we release our software to testing or the business users?



• Are there any existing contract stipulations that might prevent us from changing when we release our software to testing or the business users?

Software testing resources: The benefits of testing software by project phase Software quality and testing: Resources for beginners How to define a test strategy

There are probably other questions to ask, but that should get you started. Other questions will likely emerge as you get the answers to those. If it looks like earlier releases might be a good fit for your team, try it. If not, use the same questions, slightly modified, to determine if perhaps you're already releasing the application too early and check to see if you might benefit from slowing things down.