STARCANADA 2013: Maybe We Don’t Have to Test It
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 where you may NOT have to test can eliminate bottlenecks and make you everyone’s favorite tester. Eric shares eight patterns from his personal experiences where not testing was the best approach. Examples include patches for critical production problems that can’t get worse, features that are too technical for the tester, cosmetic bug fixes with substantial test setup, and more. Challenge your natural testing assumptions. Become more comfortable with approaches that don’t require testing. Eliminate waste in your testing process by asking, “Does this need to be tested? By me?” Take back ideas to manage not testing including using lightweight documentation for justification. Not testing may actually be a means to better testing.
Fundamentals of DevOps Certification—ICAgile
Explore the DevOps background, approach, and best practices.
Advanced Tester Certification—Test Manager
Professional training focused on areas vital for successful test management.
Agile Testing Days USA
North America's Greatest Agile Testing Festival
Software Testing Conference in Anaheim