test design

Articles

Icon showing one end to another Endgame Testing: Exploring Your Agile Product End to End

The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product.

Doron Bar's picture Doron Bar
A pile of documents Slim Down Your Test Plan Documentation

Test plans are essential for communicating intent and requirements for testing efforts, but excessive documentation creates confusion—or just goes unread. Try the 5W2H method. The name comes from the seven questions you ask: why, what, where, when, who, how, and how much. That's all you need to provide valuable feedback and develop a sufficient plan of action.

László Szegedi's picture László Szegedi
Digital wrench and gears Methods and Tools for Data-Driven API Testing

Data-driven API testing can enable feedback much sooner and more often during development while being just as comprehensive as classic functional black-box testing. There are many methods of API testing, but that shouldn't intimidate you. Testers looking to advance their careers should consider learning some coding in order to test their programs at the API level.

Albert Gareev's picture Albert Gareev
Touchscreen phone with handset Test Techniques for Today’s Telephones

Telephones look very different today from when they were first invented, and their many capabilities and components make for some interesting test cases. Krishnan Govindarajan details his team's recent experience testing a phone, including its splitter, cloud backup, voicemail and answering machine, and VoIP, and gives some techniques to use when testing modern telephones.

Krishnan Govindarajan's picture Krishnan Govindarajan
Two gears coming together Start Trusting Your Test Automation Again

The more you rely on feedback from your automated tests, the more you need to be able to rely on the quality and defect-detection power of these tests. Unfortunately, instead of being the stable and reliable guardians of application quality they should be, automated tests regularly are a source of deceit, frustration, and confusion. Here's how you can start trusting your automated tests again.

Bas Dijkstra's picture Bas Dijkstra
Mobile device lab Reduce Regression Issues by Establishing a Mobile Automation Lab

If you have a spotty test automation strategy, you may get lots of regression issues every time you have a new release for your mobile app. A mobile device lab to run regular regression tests could be the key. Here's a plan to get a mobile automation lab up and running, as well as some practices that can help reduce the number of regression issues and improve your overall app test strategy.

Saurabh  Arora's picture Saurabh Arora
Legos 100 Percent Unit Test Coverage Is Not Enough

Many people equate 100 percent unit test coverage with high code quality, but that is not enough. Code coverage tools only measure whether the tests execute the code; they make no judgment on the effectiveness of the tests. Testers should review unit tests, even if they have high coverage levels, and either help improve the tests or supplement them with extra tests where necessary.

John Ruberto's picture John Ruberto
Green lightsaber Strategies for Testing a Lightsaber (That Don’t Include the Force)

In the Star Wars saga, those in tune with the Force wield lightsabers. Lightsabers are self-built, so each one is unique and a reflection of the personality of its creator. As a tester, I found it intriguing to think about how we would test lightsabers in our own galaxy. Let’s explore how the techniques we might use for testing lightsabers can inform our real-world testing.

Michael Mak's picture Michael Mak
Continuous delivery Test Coverage in the Age of Continuous Delivery

Test coverage is a strategy to help us spend scarce testing time on the right priorities. When things were tested last, how much automation coverage we have, how often the customers use the feature, and how critical the feature is to application are all factors to consider. Here are some ideas for keeping quality high when you're transitioning to continuous delivery.

Matt Heusser's picture Matt Heusser
Slot machine QA for Slot Machines: Testing Randomization, Winning Combinations, and Big Payouts

Considering their underlying technology, slot machines are intriguing test subjects. The software at the back end randomly generates the numbers and patterns of the winning combinations, and when you add currency processing into the mix, you have some interesting test cases. If you've ever wondered what goes into testing slot machines, read on.

Krishnan Govindarajan's picture Krishnan Govindarajan

Pages

StickyMinds is a TechWell community.

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