The idea of acceptance tests — a set of tests that must pass before an application can be considered finished — is certainly not new. Indeed, the value of testing an application before delivering it is relatively well established. But the way most organizations do it comes too late in the process and is not well-integrated with the actual development process. A new approach called acceptance-test-driven development (ATDD) can change that.Traditionally, testers prepare test plans and execute tests manually at the end of the software development phase. Acceptance testing is done relatively independently of development activities. In some organizations, QA departments also use automated testing tools such as HP’s Quick Test Pro, but, again, this activity is generally siloed away from the rest of the development activity. [ 10 years on: Did agile development deliver? | Learn more about why you should adopt continuous integration development. | Keep up with the latest Java news and insights with InfoWorld’s JavaWorld Enterprise Java newsletter. ]Testing an application after it has been developed has several significant drawbacks. Most important, having feedback about problems raised at this late stage of development makes it very difficult to correct bugs of any size. This results in… Read full this story
- Testing a Software
- 4 Immediate Benefits Logging Brings to Your Software Development
- 5 Ways to Improve Your Software Design
- Waterfall V Iterative Development - Whether Or Not To Deliver Software Projects On Time
- Challenges of SOA Testing
- Maintaining Badly Written Legacy Code
- Software Product Development-the Unsolved Mystery of High Tech
- Applied Software Project Management Book Review
- Get More Marketing Value from Staffing Software
- QA / QC Engineers - What are They Doing for You?
A better approach to software testing: Do it before you code have 265 words, post on www.infoworld.com at August 29, 2011. This is cached page on xBlogs. If you want remove this page, please contact us.