Software Testing Principles Checklist

Home  >  Checklists  > 

Software Testing Principles Checklist


Login/Register to download this item








Testing is as important an activity as development on your software project.  What's more, it is many times as complicated, with a near infinite number of possible combinations of conditions and many different kinds of results to validate.  Do you conduct unit testing, integration testing, system testing, regression testing, stress testing, acceptance testing...?  Do you know the difference between validation and destructive testing and are you employing the correct ratio of one to the other?  Do you know how to reduce your testing efforts to a manageable number of activities and when to stop testing?   Who should be testing your product and when in the development life cycle should they do it?  Here's a guideline to check your testing process and see if you are testing smart or just testing.  



sponsored announcements and special offers
You can do this!
Earn your master's degree in project management without putting your life on hold at GoUWP.com!
Apply today at GoUWP.com for 100% online courses, 45 PDUs each. No entrance exam. University of Wisconsin- Platteville’s MS in Project Management is globally accredited by PMI. Combine academics and real-world scenarios for a 360-degree education.
If you have a distributed team, what are you trying to achieve with Agile approaches? Isn't Agile more for co-located teams? There are eight key benefits to working in a distributed Agile environment. A new report from ProjectsAtWork looks at each of those benefits – and how you can achieve them.
Most business and IT executives agree that any company able to rapidly deliver software of high and predictable quality with minimum budgets enjoys a significant advantage. However, practical experience shows that the challenges associated with software quality remain largely unsolved. Download the white paper Uplift Quality with Requirements Driven Testing to learn fundamental principles of Requirements Driven Testing.



"I'm glad I did it, partly because it was worth it, but mostly because I shall never have to do it again."
- Mark Twain