Testing regulated software is often seen as a tedious job that generates stacks of documentation and is subject to crippling rules. See five of these assumptions exposed as mere myths, and learn how regulated testers can use the same approaches, techniques, and tools at any other tester's disposal while still passing a process audit.
Combinatorial testing is effective for testing multiple, non-sequential inputs that affect a common output in complex software. But, it's easy to misapply it or become a slave to the output. Learn to overcome limitations and benefit fully from this technique.
Modern applications operate in highly integrated environments, and critical systems rely on massive amounts of data that likely contain sensitive information. Discover useful strategies for preparing your baseline, handling interfaces, designing input data, and planning for output results.
Test plans are seldom followed as written, project plans hardly ever fit the actual progress, and process models are rarely followed to the letter. Markus Gaertner examines why most of our documents become obsolete and gives advice about whether or not to continue to write and maintain them.
This is the true story of freedom from the monotonous work of checking. It is the story of what happened when a few passionate testers took responsibility for their own education and fun in testing. Explore how they test, learn, and contribute to the open source.
Mistakes happen. It's how you respond to them that matters. Teams might react to a bug with panic and blame, leading to a quickly hacked fix and possibly more issues. Taking time to investigate and learn leverages problems into process and practice improvement and a higher quality product.
The recent economic downturn has record numbers of job seekers pounding the pavement. Find out what you need to include on your resume to increase your chances of getting out of the paper stack and into the building for that all-important interview.
Exploratory testing is a popular approach, but many testers secretly worry they might be doing it wrong. Jonathan Kohl addresses those concerns by explaining exploratory testing in ways that testers identify with.