Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, 'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. It is oriented to 'detection'.
Reference books:
Lessons Learned in Software Testing, by C. Kaner, J. Bach, and B. Pettichord (2001)
Testing Computer Software, by C. Kaner, J. Falk, and H. Nguyen (1999)
Perfect Software and Other Illusions About Testing, by G. Weinberg (2008)
How to Break Web Software, by M. Andrews and J. Whittaker (2006)
Testing Applications on the Web, by H. Nguyen, R. Johnson, and M. Hackett (2003)
Organizations vary considerably in how they assign responsibility for QA and testing. Sometimes they're the combined responsibility of one group or individual. Also common are project teams that include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organization's size and business structure.
Hi, probably our entry may be off topic but anyways, I have been surfing around your blog and it looks very professional. It’s obvious you know your topic and you appear fervent about it. I’m developing a fresh blog plus I’m struggling to make it look good, as well as offer the best quality content. I have learned much at your web site and also I anticipate alot more articles and will be coming back soon. Thanks you.
ReplyDeleteSoftware Testing Training Chennai