test execution

Articles

Icons showing test optimization 5 Ways to Optimize Tests for Continuous Integration

Many teams have existing automated test suites that are not included in a continuous integration program. Maybe the tests take too long to execute, or they are not reliable enough to give accurate results. Here’s how to assess your test suites in terms of value added and time to execute, along with five proven strategies to optimize those suites for CI.

John Ruberto's picture John Ruberto
Medical syringes and needles Fault Injection Testing for an IoT Device

If someone says a feature is not testable through the methods we use, it does not absolve us from the responsibility of testing; that's still our job. When this team was given a new connected device to test, they realized their existing functional testing skills wouldn't be sufficient to test the product's core algorithm. So the team got creative, learning the source code and introducing fault injection, figuring out new ways to test.

Ali Khalid's picture Ali Khalid
Arrow pointing left Shifting Testing Left Is a Team Effort

There is a lot of talk in the testing world about shifting left. Basically, “shift left” refers to moving the test process to an earlier point in the development process, independent of the development approach. This article explores a case in which shift-left has been applied, and the lesson is that shifting left cannot be achieved by testers alone—it must result from a team effort.

Puzzle pieces being put together to spell "Usability" Testing to the Usability Standards Our Customers Expect

Allowing minor defects to be included in releases impacts our customers’ perspective on software professionalism. We’ll never catch every weird, obscure bug, but there are some design elements where they tend to lurk. By focusing our testing efforts on these areas—or at least not neglecting them—we can catch more issues before our customers do.

Nels Hoenig's picture Nels Hoenig
Desktop with CRM software dashboards Lessons Learned in Testing CRM Software

CRM systems manage a company’s business relationships, including customers’ data, information, and interactions, so there’s a lot that can—and should—be tested. Viktar Sachuk talks about his experience in testing CRMs to provide some tips for dealing with the trickiest parts of CRM testing, specifically focusing on some preparatory measures, functional testing, integration testing, and test automation.

Viktar Sachuk's picture Viktar Sachuk
Two golden retrievers lying on the floor, photo by Gulyás Bianka The Who, What, When, and How of Pair Testing

Pair testing can help you speed up your test assignment and provide more quality to your test results. But who can do pair testing, and when should they do it? And what kind of pair testing is best for your situation? This article gives you more information about how you should conduct pair testing in order to maximize its benefits.

Simon Schrijver's picture Simon Schrijver
Mobile phone showing social media apps Designing Test Scenarios for Social Media Mobile Apps

The definitive features of a mobile social app are the ability to send and receive messages, push notifications, and sharing media such as photos, audio, and videos. While creating a test strategy for such apps, cross-platform compatibility is an important consideration. Here are some scenarios you should include in your test strategy for a social media mobile app.

Krishnan Govindarajan's picture Krishnan Govindarajan
Car steering wheel photo by Nicolai Berntsen A Case for Test-First Development

You may feel you don't have time to write unit tests, but you really don't have time not to. Steve Poling makes the case that writing tests first not only will yield better code, but will help you get that code working right sooner. Here's how using a test-first approach changes your thinking about coding, lets you see mistakes immediately, and helps you create more testable code.

Steve Poling's picture Steve Poling
Shovel digging into dirt Uncovering Hidden Boundary Values in Testing

Boundary value analysis is a stable of test design, but sometimes the boundaries are not so obvious to the black-box tester. These are called hidden boundaries. This article provides several examples of hidden boundaries, along with some tips to design your test plan in order to reveal hidden boundaries.

John Ruberto's picture John Ruberto
Little green house Understanding Accessibility Testing: Think like a Dweller, Not a Builder

Digital accessibility aims to make any software usable by the widest possible audience. Assistive technology tools, such as screen readers, can help testers model interactions of users with special needs. But testing software design and implementation requires particular test techniques and a certain mindset: You need to think not like the builder of a house, but like the person who will make it their home.

Albert Gareev's picture Albert Gareev

Pages

StickyMinds is a TechWell community.

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