Related Content
 |
The Twelve Days of Testing On the first day of testing, the dev team gave to me a bug in the software code. This variation on the classic Christmas carol "The Twelve Days of Christmas" contains items a software tester will know all too well! |
|
 |
Getting Started with Risk-Based Testing For software development, risk-based testing is becoming a major necessity to guarantee that users are getting the best experience possible without encountering too many issues. Quality assurance teams need to effectively gauge products based on the potential risk they bring. |
|
 |
IoT Devices Are Making Test Automation Even More Critical The more devices connected to the Internet, the more challenges the average tester will face. With so many standard items expanding their technological reach through the Internet of Things, it’s becoming increasingly difficult to properly test devices manually. |
|
 |
Moving into a World of Conscious Quality Conscious quality is a quality effort that is independent, end-to-end, and stretches beyond the bounds of the core test team. If conscious quality is not adopted, we run the risk of losing the sanctity of our independence, impacting the quality of the product as well as our careers are testers. |
|
 |
The Tester as Product Owner A lot of the bugs we find were never thought through in the first place. Many of these situations are preventable, yet instead of prevention, we get the tester playing the role of the product owner—and playing it late. Why is it that we never have time to do it right, but we always have time to do it over? |
|
 |
How DevOps Is Making Testers Evolve As the streamlined DevOps movement catches on, more and more companies are abandoning “traditional testers” and getting software developers to test. Testers are not becoming obsolete—but it means testers have to evolve and start ensuring that quality is baked in. Adam Auerbach details how they need to change. |
|
 |
Why Your Agile Team Needs to Slow Down in Order to Speed Up If you find yourself rushing through development or accelerating your testing process to a speed that’s not conducive to the nature of your software or project, it might be time to take a step back, examine your methods, and find a new solution. |
|
 |
The Ethical Responsibility of Defect Severity Classification When dealing with defect classification, it's important to not blindly adhere to the criteria without consideration for real business or human implications. If your software does safety-critical work, do the defect levels reflect that? Or could something go live with potentially disastrous consequences? |
