Related Content
 |
Choosing the Right Agile Testing Tool for Your QA Team To be truly effective, QA teams have to choose the right agile testing tools for their needs and ensure that it has the required features to ensure quality and bolster testing efforts. Sanjay Zalavadia outlines a few things to consider as you search for the best solution for your QA team. |
|
 |
Artificial Intelligence’s Impact on the Future of Testing Agile has fundamentally changed the way we talk about testing. However, something that isn’t discussed as often, yet might be just as critical to the future direction of the industry, is artificial intelligence. In the world of testing, it’s easy to see how AI can be exceptionally useful. |
|
 |
Changing the Narrative: Using Storytelling in Software Testing Stories change how we think and how we perceive our surroundings. This applies at work, too. What narrative did we tell ourselves during that project? Do we tell ourselves we are worthy of succeeding, or does our story tell us to fail again? Here are some ways testers can use stories to their advantage. |
|
 |
Staying Competitive in Software Testing In today’s global economy, staying competitive may be more important than ever. Three ways to contend are by focusing on price, niche (addressing a particular group’s needs), or differentiation (doing things better in some way). Which tactic you choose could make all the difference for your software team. |
|
 |
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. |
|
 |
Go-Live Lessons: The Path from Software Development to Production On systems integration projects where a vendor is building or configuring a system for a client, you sometimes cross the canyon from development to production and maintenance in several smaller bounds rather than one big leap. A warranty period after go-live can help stakeholders confidently monitor quality. |
|
 |
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. |
