Test Design

Articles

Man looking at mountains through binoculars The Art of Exploratory Testing

Some people assume that exploratory testing is a task with low-effort thinking, where the tester simply goes through the application and sees what comes up. While we shouldn't discount doing just that, because sometimes it does reveal some interesting bugs, there are techniques and patterns that testers can follow when exploring an application. Let's look at a two-step process to use in exploratory testing.

Sanjugtha Shoba's picture Sanjugtha Shoba
Tester looking at theories posted on a wall Wish-List Ideas for Software Testing Research

There are many established ideas for ways to test software, but the industry is changing every day, and there's plenty of room for growth of new ideas—or challenges to traditional ones. Here are three ideas for "wish-list" research to conduct in order to shake up some of the conventional notions you may have about software testing techniques.

Michael Stahl's picture Michael Stahl
Person parasailing 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.

Shawn Jaques's picture Shawn Jaques
X-ray of a computer's motherboard 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.

Nicholas Snogren's picture Nicholas Snogren
Breaking through a fence to see cars speeding on a road 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.

Wolfgang Platz's picture Wolfgang Platz
Coins falling 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.

Maximilian Bauer's picture Maximilian Bauer
QA professionals performing continuous testing How Continuous Testing Is Done in DevOps

DevOps does speed up your processes and make them more efficient, but companies must focus on quality as well as speed. QA should not live outside the DevOps environment; it should be a fundamental part. If your DevOps ambitions have started with only the development and operations teams, it’s not too late to loop in testing. You must integrate QA into the lifecycle in order to truly achieve DevOps benefits.

Junaid Ahmed's picture Junaid Ahmed
Woman wearing a hard hat and working with a machine Blending Machine Learning and Hands-on Testing

As your QA team grows, manual testing can lose the ability to focus on likely problem areas and instead turn into an inefficient checkbox process. Using machine learning can bring back the insights of a small team of experienced testers. By defining certain scenarios, machine learning can determine the probability that a change has a serious defect, so you can evaluate risk and know where to focus your efforts.

James Farrier's picture James Farrier
Cards and chips at a casino Risk Coverage: A New Currency for Testing

In the era of agile and DevOps, release decisions need to be made rapidly—preferably, even automatically and instantaneously. Test results that focus solely on the number of test cases leave you with a huge blind spot. If you want fast, accurate assessments of the risks associated with promoting the latest release candidate to production, you need a new currency in testing: Risk coverage needs to replace test coverage.

Wolfgang Platz's picture Wolfgang Platz
Dozens of workshop tools laid out in an orderly fashion Transforming a Test Automation Maintenance Nightmare into Success

Best practices for test automation emphasize reliability, portability, reusability, readability, maintainability, and more. But how can your existing automated test suite adopt these qualities? Should you address these issues with your current tests, or create an entirely new set of tests? Here are some questions that will help you determine if your test automation maintenance program is operating as it should be.

Vinay Shah's picture Vinay Shah

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.