On returning to my old iOS team after a brief stint working on our services team, I wanted to implement what I had learned there and improve the stability of our Calabash scenarios. I wanted to shift away from our dependance on test data stored in config files and databases and create test data at the same time as executing our Calabash scenarios.
I’m lucky in my current role to the independence to test how I see fit. I don’t have somebody forcing me to use a tool that doesn’t work for me. After weeks of plaguing my boss to pay for a JIRA Capture licence, I eventually got my way!! I have used JIRA Capture Test Sessions briefly at a previous company and found it to be a simple but very effective tool for capturing testing notes.
The project I’m working on has an end of August deadline and over the last few weeks I’ve noticed the term MVP being thrown around with increasing frequency. Back at the start of the project, a developer dropped the ‘M’ bomb in a meeting. Before he could finish pronouncing the letter ‘P’, one of the project stakeholders very politely but forcefully interrupted the dev to remind everyone that “we are not building an MVP!”. Continue reading
Michael Bolton first highlighted the difference between testing and checking. The output of checks are binary results (true/false, on/off, black/white). Checks can be executed by humans or automatically by machines. The output of tests are questions, facts and information. Tests can only be executed by humans. Unfortunately, a lot of people continue to use these words interchangeably which can lead to confusion and mistakes. To become better testers, I believe we need to start with the basics; our vocabulary. Continue reading
Mind maps are awesome at allowing you to visualise complex/abstract concepts and link the relationships between them in a very simple format.
A few weeks back I was browsing through James Bach’s website and came across an article about rapid testing (heuristics are a central component of the rapid testing approach). A few days prior, one of the testers at work spoke about using mind maps to capture testing notes. So I decided to combine the two ideas and create a resource that would, at a glance, highlight the tools and techniques available to me as well as remind me of the testing skills I need to improve.
Little consideration is given to the opportunity cost of automation. What are the implications to the quality of software being delivered? What do we lose by focusing on the automated/coding skills of testers and ignoring their “true testing skills”? Automation is an important cog in the delivery of software but there are limits to its benefit which aren’t always fully recognised. When making decisions about automation, we all need to understand its limits and associated costs; it’s opportunity cost.