test design | TechWell

test design

Woman wearing a mask going grocery shopping 3 Software Testing Lessons from an Unlikely Source

With people trying to stay isolated as much as possible due to COVID-19, going to the grocery store suddenly became something to strategize. At least making a plan, prioritizing risk, and being agile are business as usual for software testers. Here are some of the top lessons testers can learn from our current situation.

Cynthia Dunlop's picture
Cynthia Dunlop
Basketball player playing defense Defensive Design Strategies to Prevent Flaky Tests

Flaky tests could be the result of issues in the code, but more often they are due to assumptions in the test code that lead to non-relatable results. There are many reasons that tests can fail intermittently, and some can be easily avoided by applying good defensive design strategies. It's all about making your code agile.

Steve Berczuk's picture
Steve Berczuk
Sign with an arrow pointing toward the word "Strategy" Figuring Out Your Regression Testing Strategy

When your application is scheduled to go to production, the development team may be asked what their regression testing strategy is. This is a perfectly reasonable question, but a lot of people have a hard time answering it. Don't overcomplicate it. Analyze your process, look at the other testing, and put it together.

Justin Rohrman's picture
Justin Rohrman
Scientist holding up a slide with a plant on it to examine it Reality-Driven Testing in Agile Projects

Agile teams can drive down rework and devise more useful tests quicker by prioritizing reality-driven testing. This means tests based on reality, or relevant test activities above and beyond those derived from requirements. Learn some strategies to get real and design tests to locate important bugs that truly matter.

Robert Sabourin's picture
Robert Sabourin
Person creating tests with code 2 Ways to Get Better at Test Automation

Many people in testing roles want to grow their skills and learn to build some tests with code. But no matter how well you test, automation is programming work. If you want to get better at automation, your best bet is to get into a role where you are dealing with code. Here are two ways you can break in and learn.

Justin Rohrman's picture
Justin Rohrman
Stack of product boxes Why You Should Treat Tests as Products

There's a case for treating some of your tests as products—project deliverables in their own right, created as a business investment. "Productizing" tests can show their value to management, but more importantly, it can help them contribute more effectively to the development lifecycle. Here are four steps to consider.

Hans Buwalda's picture
Hans Buwalda
API code on a laptop Why API Testing Is Mission-Critical

With API testing, if you change how the API works—even if it now works better—it will break all of the code written by people using the API. Consequently, testers have a responsibility to make sure they are testing the same contract that was established when the API was first released. Here's how to test APIs right.

Adam Sandman's picture
Adam Sandman
Software professional exploring test cases using design thinking Using Design Thinking to Create Better Test Cases

Design thinking is a user-centric framework to solve a business challenge by delivering the best user experience. Using design thinking, you can better frame the business drivers, select the right persona to focus on, design your user journey, identify test scenarios, pinpoint user pains, and write better test cases.

Larissa Rosochansky's picture
Larissa Rosochansky