user experience

Mukesh Sharma and Rajini Padmanaban of QA InfoTech sit down to talk about their upcoming book, Leveraging the Wisdom of the Crowd in Software Testing. In this interview, Mukesh and Rajini also talk about the benefits and future of crowdsource testing.

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.

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.

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.