The Latest

Test teams must perform a wide variety of tasks from testing new functions and performing regression tests to helping with bug fixes, producing test reports, and working on test improvements. With all these activities, it is a challenge to keep priorities straight, operate most efficiently...

Testers are taught they are responsible for all testing. Some even say “It’s not tested until I run the product myself.” Eric Jacobson believes this old school way of thinking can hurt a tester’s reputation and—even worse—may threaten the team’s success. Learning to recognize...

Large, complex projects—those with more than 100 people and lasting more that a year—require special considerations for developing, communicating, and managing the overall QA strategy and test plans. Shaun Bradshaw provides insights he gained from a $70 million financial...

Jamie Mitchell explores perhaps the most underused test technique in our arsenal—white-box testing. Also known as structural testing, white-box requires some programming expertise, access to the code, and an analysis tool. If you only employ black-box testing, you could easily ship...

Testing projects have a habit of dissolving into chaos—and even strife—as deadlines approach and budgets are cut. When asked to do the impossible, risk management and mitigation tools can be the only way for testers to survive. Geoff Horne presents a proven method he uses for...

The burgeoning use of mobile devices has created enormous opportunities for organizations to leverage mobile to increase sales, advertise products, and collaborate with internal and external resources. However, with increasing usage, the need to perform testing on these devices is...

Traditional processes have required testers to create a large amount of documentation in the form of test plans, test cases, and test reports. It’s time to think differently. Creating test artifacts in the “old school” textual style takes too much time away from actual testing.