Related Content
 |
What to Do When Bugs Are Found—Based on When They Are Found When executing test modules, an interesting question to ask is “What needs to happen with issues that are found?” Hans Buwalda suggests making a distinction between issues found during a sprint and after the team has declared the functionality under test "done"—and describes how to proceed from there. |
|
 |
Test Automation Is Mandatory, Thanks to Agile Unlike waterfall, where people had to do their best to explain the value of automation, agile more naturally promotes that need for these tools through its rapidity and integration of testing throughout the development process. Agile assumes automation is the key ingredient of your mission strategy. |
|
 |
Before Jumping into Software Testing Tools, Get Your Code Straight Software testing tools can be incredibly helpful, but only if you're implementing them from a good starting place. If your code is a mess, a tool won't fix that; you'll end up simply adding layers on top of the mess. Matt Heusser explains how your team would be better off learning elements of code as craft. |
|
 |
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. |
|
 |
Necessary Skill Sets for the Agile Test Team In making the move to agile practices, testing teams are finding that a specific skill set—or more than one—is necessary in order to take advantage of the benefits of agile methodologies. Sanjay Zalavadia looks at the skill sets and information that teams need before an agile project can begin. |
|
 |
Fine-Tuning and Expanding Your Mobile Test Plan When new technology is introduced, QA teams usually have a period of scrambling to figure out how to support engineering efforts. Melissa Tondi identifies some key mobile challenges and talks about creating solutions to address them. The result: an efficient mobile test plan and minimal impact to the QA team. |
|
 |
What’s in the Spring 2016 Issue of Better Software Magazine? The spring 2016 issue of Better Software magazine includes a number of articles that emphasize state-of-the-art practices in testing, metrics, and controlling technical debt on mobile software development projects. Read on to see how this issue can help you improve your processes and rethink workflows. |
|
 |
Test Automation—A Non-Expert’s Perspective Looking at automating test execution, there are two distinct areas of focus—testing at the technical level (component and technical integration) and testing at the functional level (system or acceptance). Dale Perry offers his view on each's requirements, focus, and the issues that can arise. |
