Related Content
3 Reasons Exploratory Testing Is Great for Agile Teams Specification-based testing is critical for determining whether a user story is “done done.” But that doesn’t ensure a positive user experience. Coherence, comprehension, and usability are beyond the scope of automated functional testing. Here are three reasons agile teams should embrace exploratory testing. |
||
3 Essential Components to Building a Security Testing Practice Most mobile app development teams lack a security testing practice, or if they do have one, it lacks the maturity to be effective. But the great security practices are not necessarily those that spend the most money or have the most engineers. It’s the ones that have adopted these three fundamental concepts. |
||
Why Testers and Developers Don’t Have to Be on the Same Page Since software development is highly subjective in nature, different thought processes and assumptions between development and testing teams can positively impact applications and lead to a more successful, well-rounded product. It might not seem like it at the time, but there’s value to dissonance. |
||
Where to Begin with Test Automation Most test teams want to try automation for some tasks in order to be more efficient, but it can be daunting. If you are wondering where to start automating, the answer is usually as close to the code as you can possibly get. The farther you get from the code, the more you expose yourself to issues. |
||
3 Fundamentals of a Successful Testing Team When it comes to equipping a QA team to reduce risk, test quality, and deliver world-class products, there are more important things than tools. Fundamentals such as a common language, core testing concepts, and a smart automation strategy are essential to setting up testing teams for success. |
||
Your Test Automation Framework Is Just as Important as Your Tools If you don’t have the proper automation framework, the actual tools you use don’t pack near as powerful a punch. This framework allows you to better organize your reports and develop metrics through your test automation. |
||
How to Choose the Right Test Cases to Maximize Efficiency For test teams, throwing every test case in the book at a project isn't practical or necessary. By understanding test design techniques and what to look for in a good test case, teams can choose the ones right for their requirements and improve their testing efficiency. |
||
Reviving the Master Test Plan in the Age of Agile In the competitive environment of delivering software more quickly, many teams have abandoned detailed test plans. Michael Sowers argues for bringing back the overarching master test plan—not to have more documentation, but for the questions, creative test designs, and critical thinking the planning brings. |