I have been a functional exploratory tester. I was motivated to move out of exploratory testing and become that cool kid doing automation. Thankfully, someone pulled me aside and told me - I am more suited to be a functional exploratory tester and that I am business savvy. I didn't shy away from code. I worked closely with developers and my testing approach involved reading code (didn't write any) and brought in value to developers and to the business. I grew up as a tester being coached by experts, reading blogs from experts and learning that automation will help exploratory testers do more.
In my wait - I found very little effort that has gone in direction. I partnered with developers to be building some products.
I failed multiple times and here are my failed attempts
- Tool for Social Media Driven Testing for Testers
- Tool for mapping the heuristics and oracles to test ideas
- A checklist tool for testing mobile apps and scoring on quality for start-ups
- Testing Depth Dashboards
I would like to share
- The thinking behind building these tools and their value
- How purely focusing only on automation is taking away the possibility of building tools
- How I would love the community to start building tools
- How I can help the audience (without commercial interest) and how they can help me
I would like to tell my own story and how I (actually stealing credit from my team who build it) came to build tools
- What I did different from other manual testers?
- What problems concern testing space according to me
- The problems I picked and the way I tried solving them
- The failures and analysis
- The existing opportunity for people to build value different from automation frameworks and scripts
- The vision of open sourcing non code deep thinking tools for testing
