test methodologies
The Importance of Testing in Conjunction While it is important to have distinction between testing efforts to maintain specialization and core subject matter expertise, having overlap in test efforts—testing in conjunction—is becoming a common practice. |
||
How Retrospective Meetings Can Improve Your Team's Software Quality Efforts Many software professionals think they won't get anything out of retrospective meetings and want to cut them out entirely. However, retrospective meetings are a necessary part of project progression, and they can significantly improve your team's software quality efforts. |
||
Building a Business Case for Automation in Your Software Lifecycle To remain competitive, organizations should consider implementing a well-integrated set of automation capabilities—not just for testing, but across the entire lifecycle. Making the investment might take some convincing, so here are some questions to ask in order to assess the potential benefits of automation. |
||
3 Steps to Nurture IoT Development and Testing As more devices connect to the Internet and engage in machine-to-machine communication, QA management must cultivate an understanding of the IoT and how to create software for these connected items. Sanjay Zalavadia describes three steps to nurture IoT development and testing. |
||
Automation Friendly Test Design—An Example A major contributor to success in test automation is test design. If tests have many unnecessary detailed steps and checks, even a skilled automation engineer will not be able to make the automation efficient and maintainable. Hans Buwalda shares an example of a test design that is automation friendly. |
||
The Top 5 Test Automation Mistakes Test automation is a valuable process, but it can be difficult to integrate into your existing test strategy. Melissa Tondi talked to hundreds of people about the biggest mistakes they’ve made when automating. Here are five of the most popular answers—and advice on how we can stop repeating these mistakes. |
||
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. |