The Latest

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

Overcoming organizational bias toward software testing can be a key factor in the success of your testing effort. Negative bias toward testing can impact its perceived value—just as inaccurate positive bias can set your team up for failure through mismanaged expectations. A structured...

Jamie Mitchell explores an underused and often forgotten test technique—white-box testing. Also known as structural testing, this technique requires some programming expertise and access to the code. Using only black-box testing, you could...

Test automation scripts are in a constant state of obsolescence. New features are added, changes are made, and testers learn about these changes long after they've been implemented. Marcus Merrell helped design a system in which a "model" is created each time a developer changes...

The last exciting era in testing was the late ‘90s when the web turned technology on its ear, the agile movement overthrew our processes, and the rise of open source gave us accessible and innovative tools. However, since then, Jonathan Kohl finds it has been a lot of the same-old, same-old.

Many smart, otherwise-capable testers sabotage their own careers by committing one or more of the deadly sins of testing: irrelevance/redundancy, ignorance of relevant skills, obstructionism, adversarialism, nit-picking, blindness to project/organizational priorities, and last-moment-ism.

If testers sit passively through agile planning, important testing activities will be missed or glossed over. Testing late in the sprint becomes a bottleneck, quickly diminishing the advantages of agile development. However, testers can actively advocate for customers’ concerns while...