Category Archives: QA
Usability testing for your information architecture – before you code.
Written in collaboration with Efrat Wurzel Three things some testers say that should serve as a warning sign that you may not want to hire them: “I can’t understand a feature or start thinking about its tests until I use … Continue reading
If you’re testing HTML5 mobile apps, you might want to read about code injections through the bar-code scanner, videos, Bluetooth and more.
If you’re working on a product and have no particular understanding of UX, you can still do a basic UX review to stop the most obvious disasters. This will not be as good as getting a UX expert or experienced … Continue reading
We’ve all worked with testers who were bad at their job; it was frustrating and felt like a giant waste of time and effort. But hold on to those bad testers: they’re more useful than you think.
Some bugs, even quite severe ones, can seem to your users like very nice features. Bugs that are likely to reach this status are those that make work smoother at the expense of security (for example, not enforcing part of … Continue reading
Technical writers have a very clear goal: explain the interface. That means they notice, instantly, when it’s inexplicable. If your interface is a confusing mess with overly-complicated procedures, buttons that make no sense, important options hidden in sub-menus and related … Continue reading
Some bugs are a work of art. Consider a login page I encountered a few weeks ago. Two fields, one Submit button – so far so obvious. But above the button was the text “Do not press Enter to log … Continue reading
Lessons I Learned as a Tester, 4: Testers Should Write the First Draft and Approve the Last Draft of Release Notes
You might say I learned this lesson as a technical writer, too.