test methodologies

Articles

Testing Value Considering the Value of Software Testers

Many people think software testing is just about verifying from a checklist that functions do or do not appear. But what if more testers spent time looking at the product's behavior? Testers working with product owners, a development team, and other stakeholders can compare their understanding of the software and ask the crucial question, “Will this meet our needs?”

Peter Walen's picture Peter Walen
Testing Your Apps Picture Imperfect: Methods for Testing How Your App Handles Images

On a website and in digital files, images present a set of complications and differentiations that you need to keep in mind when your application receives and presents them. Your application might rely on a library, plugin, or service built somewhere else to handle this image management, so you should test the image uploader to ensure it works correctly and handles common points of failure. Here are some things to watch out for.

Brian Noggle's picture Brian Noggle
Automation is Not God Automation Test Suites Are Not God!

In today’s age of tight deadlines and accelerating delivery cycles of software, test automation is surely favorable for the world of functional testing and critical to the success of big software development companies. But its various benefits have led to unrealistic expectations from managers and organizations. This article highlights the role and use of automation in an agile context and the irreplaceable importance of manual testing.

Nishi Grover's picture Nishi Grover
Requirements for Testing 3 Types of Requirements for Testing

Requirements for software are usually grouped into a bewildering array of categories. Functional and nonfunctional requirements are on top, and a huge number of subcategories are underneath. Here, Clint Hoagland boils it down to three categories, differentiated by the way they should be tested.

Clint Hoagland's picture Clint Hoagland
Testers Quality Standards When Testers Should Stand Up and Say No

Testers often find themselves in predicaments where they may be asked to compromise on quality standards—whether it's pressure to sign off on a product before it's ready, getting involved in numbers games that value metrics above all else, or facing harassment to take on work that isn't theirs. Knowing when, how, and why to say no can improve your situation and gain respect for testers everywhere.

Mukesh Sharma's picture Mukesh Sharma
Global Software Testing How to Think Globally about Software Testing

The global reach of your software could be stalled because of improper design or late detection of bugs. To release software to be used in more than one country successfully, you should try some tactics you might not usually employ. Consider these special approaches to keep a global mindset when testing.

Anuj Magazine's picture Anuj Magazine
Testing Requirements Redistributed Testing: A Shift to Refine Requirements

In short, redistributed testing is a shift in the emphasis and responsibility for testing. Testers are reassigned to work closer to the business with users or business analysts or are embedded in the development team.By being involved in story and scenario writing, the testers help to refine requirements and improve their quality. How could your systems benefit from redistributed testing?

Paul Gerrard's picture Paul Gerrard
Exploratory Testing Exploring Together: Shared Understanding Through Paired Exploratory Testing

As a ScrumMaster, Claire Moss is responsible for removing obstacles for her team. In this article, she describes her experience teaching everyone on the team—testers and non-testers—exploratory testing skills through pairing.

Claire Moss's picture Claire Moss
Software Product Discovery How a Software Tester Helps During Product Discovery

A software tester can begin testing early—very early—before the software has even been built. Karen Johnson explains that one of the best times to start testing a product is in the product-discovery phase.

Karen N. Johnson's picture Karen N. Johnson
Fixing the Brittleness Problem with GUI Tests

One common complaint about test automation is that it’s too brittle. Small changes in the system can cause lots of rework during the automated checks. In this article, Clint Hoagland shows a way to fix “the brittleness problem” by using the right abstractions in your automation design.

Clint Hoagland's picture Clint Hoagland

Pages

StickyMinds is a TechWell community.

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