Tag Archives: Lessons learned
In a lot of offices, if you’re not typing or clicking – you’re not working. It’s an odd view for any member of an industry that prides itself on thought and creativity. To analyse a problem, understand it and come … 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
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.
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 … Continue reading
The further away you are from the QA department, the looser the definition of version sanity. By the time you get to the back of the development department, where the newbies sit, the definition of sanity is “compilable”.
When asked to provide testing instructions for a new feature or bug fix, there are three types of developers: some are surgically precise, some are fairly precise while erring towards caution, and some give the widest set of instructions they … Continue reading