test techniques

Articles

puzzle The Collaboration of Unit Testing

Unit testing can be one of those polarizing topics in software development. But Joe DeMeyer says good unit testing allows you to explore products deeper, lowers your estimate, improves quality, and maintains productivity pace. Here, he talks about how you can get your developers and business team on board.

Joe DeMeyer's picture Joe DeMeyer
mobile apps Testing Usability for Mobile Applications

Mobile usability goes a long way in enhancing end-user app acceptance. But usability starts with the user, and users differ in terms of knowledge, interests, goals, and so on. This article discusses some core usability characteristics that matter to customers, and how test engineers can understand and achieve them.

Mukesh Sharma's picture Mukesh Sharma
Zombie data Site of the Living Dead: Defending against Zombie Data

The dead walk among us. Both humans and data declared digitally deceased are actually alive, and the information saying otherwise is doing continued harm. These are the harrowing tales of zombie data, where death takes on a twisted meaning and what is dead may not stay dead. Spooky!

Lanette  Creamer's picture Lanette Creamer
Wearable smartwatch Testing Wearables: The Human Experience

When a networked device is physically attached to us and works with us and through us, the more personal, even emotional, the interaction is. With wearables, the user becomes a part of the Internet of Things. Gerie Owen realized that consequently, a human user must be an integral part of testing wearables. Here, she details this human experience testing.

Gerie Owen's picture Gerie Owen
Pulp Fiction Why Every Software Tester Should Watch Pulp Fiction

The 1994 movie Pulp Fiction is a modern classic. And its eclectic dialogue, groundbreaking cinematography, and dramatic flair actually provide good inspiration to talk about a few things every tester has probably experienced in his or her career. Here’s how plot points and film techniques in Pulp Fiction mirror some experiences in software testing.

László Szegedi's picture László Szegedi
Flow chart algorithm The User and the Algorithm

When testing, it's easy to call problems with how you'd use the software out of scope, dismissing them as "-ities," like usability, scalability, or security. Some test teams explicitly carve off all these concerns and say they are only dealing with functional testing. Yet the questions raised by this sort of thinking can lead directly to high value for customers.

Matt Heusser's picture Matt Heusser
Continuous cycle The Power of Continuous Performance Testing

Continuous performance testing gives your development teams a fighting chance against hard-to-diagnose performance and load-handling bugs, as well as quickly identifying major functional bugs. Due to its combination of flexibility, coverage, and effectiveness, performance tests are powerful candidates for continuous testing.

Don Prather's picture Don Prather
Thinking cap Want More Innovative Testing? Put on a Different Thinking Cap

Testers commonly face challenges around one-dimensional thinking, limited ideas, and communication issues. Sometimes, all you need to break out of a comfort zone or come up with better approaches is a fresh perspective. Putting on a different “thinking cap” can help you innovate solutions in a whole new way.

Rajini  Padmanaban's picture Rajini Padmanaban
Help keyboard button Overcoming Cognitive Friction to Engineer Better Software

The problems customers face are difficult to anticipate while developing software. However, looking at support issues can give a clearer idea about how to look for defects in the future. Sometimes users don’t know how to find certain information; other times, software doesn’t work as expected. In both cases, cognitive friction is at play.

Nilanjan Bhattacharya's picture Nilanjan Bhattacharya
Evidence of software testing “How Was This Tested?” Providing Evidence of Your Testing

Many testers have a tendency to minimize the information they record when testing. The challenge comes when problems are found later, possibly after the software is in production. How do we remember what we did, and when? What records do we have to refer to? How do we, as testers, answer the question “How was this tested?”

Peter Walen's picture Peter Walen

Pages

StickyMinds is a TechWell community.

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