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.
As with any other quality attribute, it is ideal for accessibility to be incorporated in the early stages of design and engineering. But organizations that didn’t initially take accessibility into account can still address it now—it’s better late than never. Here are the main attributes you should consider from the design, development, and testing angles, whether you're building accessibility in from the beginning or adding it now.
If you're uncertain about where to focus your testing or what kind of testing you should be doing, look at what your users are telling you. Understanding the analytics of how your customers use your application can help you improve your test efforts. This article explores instances of how this data can inform user interface automation, compatibility testing, and web services tests.
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.
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.
Many companies creating mobile apps struggle to find the time to test on a variety of devices, organize bug reports, and resolve issues efficiently. Andrew White’s organization tried Ubertesters, a platform that provides a team of mobile testers and a set of features for feedback. This is his account of how it affected their test process.
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.
"User experience" and "usability" are often used synonymously, but they are actually different concepts. This article examines both terms and explains the components of each, investigating what contributes to a "good user experience," the different ways that can be judged, and how designers can attempt to achieve it.
Selecting a testing tool is hard work. If you look on vendor websites, you'll get marketing material promising the world. If you look on forums, you'll mostly get people trying to solve their own problems. Justin Rohrman tells you why you might choose Selenium as your UI testing tool, based on real experience with real software projects—rather than a marketing page.
When developing products, features, and enhancements, you have to have your customers’ best interests at heart. “We’re not just creating software,” speaker Jeff Patton said. “We’re changing the world.” You need to better understand the people you’re building things for, and the only way to do that is to spend more time with them.