Test Design

Articles

Person writing down rules for software testing in a notebook The Simple Rules of Software Testing

Simple rules are great for guiding us through an overwhelming workload. Sometimes complicated solutions are necessary, but simple rules often outperform complex algorithms, making them more efficient than sophisticated, difficult flows. They can also break down big goals into practical daily guidelines testers can follow to perform more effectively. Let’s see how simple rules can be applied in software testing.

László Szegedi's picture László Szegedi
Person comparing two apples An Automated Approach to Regression Testing

Testing every single thing isn't feasible, so regression testing should be holistic in verification while focused in scope. A good goal is to ensure no regression issue is introduced into a critical business flow. This endeavor can benefit from automation. An automated testing approach specific to reducing regression issues can go a long way toward building a good client relationship and high brand value.

Anubhav Bansal's picture Anubhav Bansal
Person using a screen reader Fitting Accessibility Testing into Agile Development

The concept of accessibility has been around for more than twenty years, yet it’s only recently that more companies have started including it in their development efforts. Developers and testers are recognizing the advantages of incorporating accessibility techniques into their processes. Here are some of these methods specific to agile software development, including a handy checklist.

Albert Gareev's picture Albert Gareev
Person holding magnifying glass up to computer screen to find a bug 6 Ways Testers Can Add Value (Other Than Functional Testing)

Many testers spend their time doing functional testing and don't come out of this cocoon. But software testing is all about discovering quality-related information to assist stakeholders in making informed decisions, and there are multiple ways to discover information in addition to functional testing. Here are six actions that will help you add more value to your projects.

Ajay Balamurugadas's picture Ajay Balamurugadas
Michael Bolton Is All Testing Exploratory? A Slack Takeover with Michael Bolton

Thought leaders from the software community are taking over the TechWell Hub for a day to answer questions and engage in conversations. Michael Bolton, a speaker and thought leader in the testing industry, hosted this Slack takeover, which led to discussions about test exploration, tools, and testers as gatekeepers.

Owen Gotimer's picture Owen Gotimer
A piece of plain paper laid over a pile of other paper with typed words Overcoming Challenges to Good Test Documentation

Getting good test documentation is a consistent challenge. Agile proposes that you should go very light on documentation, and while test documentation does not need to be heavy, it does need to be clear and cover all that the product is intended to do so you can ensure testing is consistent and results are recorded. Here's how to overcome some major barriers to getting good test documentation.

Steven Penella's picture Steven Penella
Red octagonal stop sign 3 Testing Practices We Should All Stop

Testing evolves, and it becomes clear that some concepts we’re all used to doing are no longer applicable today. It’s important to periodically take stock of our testing practices and cull the ones that no longer make sense—or are downright harmful. Here are three common testing practices it’s in our best interests to stop doing.

Ajay Balamurugadas's picture Ajay Balamurugadas
Test pyramid with the base unit test layer eroded The Eroding Agile Test Pyramid

The test pyramid is a great model for designing your test portfolio. However, the bottom tends to fall out when you shift from progression testing to regression testing. The tests start failing, eroding the number of working unit tests at the base of your pyramid. If you don't have the development resources required for continuous unit test maintenance, there are still things you can do.

Wolfgang Platz's picture Wolfgang Platz
Chefs preparing and cooking food Taste-Testing: Cooking Up Good Software

Think about what we do while cooking food to make it the best dish possible. We taste the food first, make necessary adjustments and add a few more ingredients, taste the food again, and repeat until the dish is how we want it. This is just like building a software product. If you don’t taste the food before serving it—or test the software before rolling it out—there will be a risk that the quality isn’t up to your standards.

Arun Kumar Dutta's picture Arun Kumar Dutta
Power button Simplify Continuous Operation Tests with a Periodic Reboot

Continuous operation tests find important bugs, partly as a result of their long operation and partly by increasing the probability of finding statistical bugs. However, CO tests have their own downsides. Mandating a periodic reset or reboot can work around these issues, as well as save time and cost for testing, reproduction, debugging, and fix verification.

Michael Stahl's picture Michael Stahl

Pages

StickyMinds is a TechWell community.

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