 |
Fitting In Regression Testing by Shifting QA Left Fixing a bug in one area of the software may break something in another area. To detect whether defects have been introduced, we need to perform regression testing—executing certain test cases again to see whether a change has affected other existing features. But how do you make time for another testing cycle prior to every production release? You need to get QA involved earlier in the software development lifecycle. |
|
 |
False Errors in Test Tooling Traditional GUI automation is linear; it follows a set of steps. The first time you run it, it can't add any value, as the feature isn't done until the automation runs. Once test automation runs a second time, it effectively becomes change detection. This leads to a large number of "failures" that are not actually failures. Whether they are false positives or false negatives, we need a way to fix the automation tooling. |
|
 |
5 Steps to Getting Started with Risk-Based Testing Risk-based testing is an approach to testing that helps us handle our limited resources. It’s also a valid model for years to come because it focuses testing resources where they can have the most impact—regardless of whether limitations are due to budget, tight schedules, or even the uncertainty of an unexpected situation like COVID-19. Here are some practical tips, examples, and steps you can use to adopt risk-based testing. |
|
 |
How to Respond to Retest Requests without a Clear Bug Fix After finding and reporting a bug, a tester may get this response from a developer: "Please rerun the test on the latest version of the code and check if the bug still reproduces." This seems like a rational request; just as a change can cause a bug to appear, it can also fix a bug. But is following up the responsibility of the tester or the developer? And if the bug is no longer there, how do you classify and close it? |
|
 |
X-ray Vision and Exploratory Testing Imagine you have X-ray vision. Instead of seeing through walls, you can see the inner structure of programs, the bugs lying inside, and how to expose them. Anyone could execute the steps you gave them to reproduce the bugs. The difficulty in testing, then, is not in executing steps; it is figuring out what steps to take. How do you find those hidden bugs? We need to be the X-ray vision. |
|
 |
Enterprise Test Automation: 4 Ways to Break Through the Top Barriers How can mature companies with complex systems achieve the level of test automation that modern delivery schedules and processes demand? There are four strategies that have helped many organizations finally break through the test automation barrier: Simplify automation across the technology stack, end the test maintenance nightmare, shift to API testing, and choose the right tools for your needs. |
|
 |
The Hidden Costs of Automation While automation can help you save time and money in your testing activities, there are a few hidden costs that many teams overlook. Aspects that don't have a price tag initially—such as what it will take to learn, adopt, and maintain a new automation tool—will end up costing you in the long run. Think through these considerations and answer some questions before jumping into your automation initiative. |
|
 |
How to Accelerate Your Release Cycles with Agile Testing With the traditional waterfall method of testing, achieving quality and faster time to market is difficult. Agile testing has emerged as an alternative, where development and testing take place simultaneously instead of operating in their respective silos. Let’s look at what it means to perform agile testing, what practices are necessary, and how agile testing can benefit your software releases. |
|
 |
Testing in Agile: How to Get Started There is a lot of interest in organizations around a transformation to agility. However, the focus is usually on agile development, so it may not be clear how software testing is done in agile. If you're responsible for leading your testing teams, don't let them be left behind. Here’s how you can make testers part of the transformation, too—step by step, because this is agile, after all. |
|
 |
Where Your Money Is Lost in Testing Companies that want to reduce testing costs usually try working with fewer people, or even cutting back on the amount of testing done. But with those approaches, quality usually suffers. Releasing a critical bug and suffering the subsequent pain usually costs multiple times what testing would. There are better ways to save money, and it can be done just by being smarter about our test cases and their structure. |
Pages
Upcoming Events
| Oct 01 |
STARWEST Software Testing Conference in Anaheim & Online |
| Nov 05 |
Agile + DevOps East The Conference for Agile and DevOps Professionals |
| Apr 28 |
STAREAST Software Testing Conference in Orlando & Online |
