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 UX-QA to review the product, but it will be much better than nothing.
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 the permissions mechanism), faster by letting users skip steps that should be mandatory (for example, […]
The only way to improve, the internet keeps telling us, is to push yourself past your comfort zone so that you’re always learning new things. Writing day in and day out, however, can mean you start to churn out documents on semi-automatic, settling for your current skill level and never improving. In fact, some of your skills, […]
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 in; use the Submit button”. I pressed Enter, of course: the page was refreshed and […]
There is a general problem in software, more pronounced in minimalist Agile efforts, of documents that look good at the time of writing, but do a poor job of transferring information. I call these “stump” documents because readers are stumped when they try to learn from them.
You might say I learned this lesson as a technical writer, too.
As a lead tester, you fall somewhere on a scale between being completely passive about bug fixes and being in complete control of them. If you are completely passive, you are managing neither the product nor its quality. If you are in complete control, you are managing both. Neither of these situations is good for […]
Written in collaboration with Efrat Wurzel The basic premise of QA is that developers – being human – make mistakes; but too many testers think that developer mistakes are limited to the code they write. The truth is that developers can misunderstand the spec, forget a part of it, never notice that a spec is […]
These questions are for experienced candidates, not aspiring writers, and are meant to reveal general attitudes and methods. You want to see how people think, and how they act and react to other writers.