I see humility as a very good virtue. It is something I have failed miserably at, partly because it is easy to think something is bad just because there are many problems. I think it’s a common fallacy for many ambitious testers – you are last in line, maybe with lower status, you want to […]
Status reporting of testing activities is extremely project-dependent. The needs of when and how and what will differ every time. Maybe that’s why there’s so little good writing about status communication; you have to make it up every time. Templates are out of the question, and I believe examples will mislead you as well. You’re […]
Generic test report: DateTime ID Author Time for writing report Time maintaining scripts for generating report Application Under Test Areas tested For each area: Blockers Testers Tester mood Tests planned Tests executed Tests passed Tests failed Tests remaining (untested+fail) Bugs found, per priority Old bugs status (priority, severity, tester, assignee, days active) Bug resolution aggregation […]