Related Content
Improving Test Automation—What About Existing Tests? A good test design is important because it improves the quality of the tests, helping to add breadth and depth, and it facilitates efficiency, in particular for automation. These points are obvious when starting a project from scratch, but what do you do when tackling a project with existing tests? |
||
Adapt or Fail: Why Mobile Development and Testing Need to Be Agile When it comes to effective and efficient mobile app development and testing, transitioning to agile has almost become a requirement. Agile allows you to make amendments at any stage of the process, both welcoming change and using it as an advantage. |
||
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. |
||
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. |
||
How Do We Sell the “Test Early” Principle? Many companies are striving to test earlier. But goals and principles are always easier to articulate than they are to implement. Often, this is less of a technical issue and much more an organizational, change management challenge. Michael Sowers talks about the steps to take to make things happen. |