Author Archives: Irit Arkin
A spec that can’t be tested is a starting pistol in a treasure hunt. The treasure is information, but not any old bit of information – you, as a tester, must get the same information that was given to the programmers.
Oliver Burkeman reviews the basics of thinking about writing.
From time to time I teach people some QA basics. I do this at start-up companies, since most established companies have someone in-house to train QA. A couple of times I trained experienced testers who only had to transition to … Continue reading
Agile got (at least) one thing right: stop writing documents no one’s ever going to read. If you want to honestly assess what will or won’t be read – and therefore what should or shouldn’t be written – you should … Continue reading
Tools of the trade, 2014. Everything from bug tracking to HR.
First let me clarify – I’ve nothing against HR and their involvement in the hiring process. What I object to very specifically are two habits: letting HR choose who gets interviewed, and letting HR do the first interview and veto … Continue reading
Usability testing for your information architecture – before you code.
Three things some technical writers say that should serve as a warning sign that you may not want to hire them: “I only need to understand it at the UI level”. If you don’t understand how and why things happen, … Continue reading
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.