Subscribe to the full blog feed using RSS
TLDR: When we use multiple tools and existing tool features, we open up new options in how we approach our testing. This can help us identify workarounds when we identify testability feature requests, and might even remove the need for the testability feature.
I set myself a Practice Test Exercise. You might want to try it yourself before reading the full text of this post.
TLDR; Apply MVP principles when coding. Code to the API first. The API is internal before it is external. Unit tests with classes. In code testing with classes in combination. In code API testing. External HTTP API Testing. And then if necessary -In memory and process HTTP API testing. GUI.
A long time ago, in a town which I no longer live in, I wrote a tool called Compendium-TA
Commercially that was a disaster: it was self funded, it took a long time to write and I made some poor technology decisions.
I learned MVP and API First Thinking the hard way. I’ll try and explain within.
TLDR; Mobile device connects to travel router making wireshark easy, and easier traffic capture.
I think, although I can’t find the blog post, that I’ve described use of a Travel router for mobile testing before.
But my TP-Link TL-MR3020 no longer seems to work with my Macbook - now upgraded to a newer MacBook Pro with USB-C connectors.
I spent too long trying to get it working so in the end I just bought a new Travel router.
I tried the TP-Link TL-WR802N and now it all works fine.
TLDR; Testing driven by technical understanding seeks to observe at multiple levels of the application stack and the testing conducted is informed by identifying risks in a model built by observing the application below the GUI.
I created a short live exploratory testing video using Orange HRM
When I was preparing for the London Tester Gathering workshop I decided to try and fix a flaw in my docmentation workflow.
The flaw was - I find it hard to have an overview of my documentation while working with Markdown. I fixed it with Freemind and a custom script.
TLDR; Recording of my Agile Tour London 2017 talk is now publicly available on InfoQ
Back in October 2017 I spoke at Agile Tour London on the topic of how Software Testing fits into the Modern Software Development process.
My recording with the slides and mp3 downloads are also available on Evil Tester Talks
TLDR; Notes on Shift Left, where I try to explain why I don’t use the term and what I use instead. Evolve, Grow and Improve rather than Shift and Move
For some reason I’ve had a few emails and linkedin questions asking me what I think about “Shift Left”. I thought I’d put out a public answer.
I’ll start with - I do not use the term “Shift Left” because:
- It seems like “consultant speak” and, while I’m a consultant, I try to speak clearly
- It obscures, rather than clarifies, whatever point it is trying to make
- It makes me think of ‘moving a whole thing’ rather than improving the System
Instead I think of supporting the growth and evolution of a System over its lifetime and I don’t need “Shift Left” to do that.
Back in 2011 I started to document migration steps from Selenium 1 to Selenium 2.
I created a workshop to support people migrating and seem to have converted into a ‘book’ format between 2011 and 2014.
Time to release it as Open Source.
I was tidying up some old papers and found an article I had forgotten I had written. “The Question: Are there any Software Testing Superheroes?”
This appeared in the Eurostar magazine that was handed out at Eurostar 2013. I can’t find any mention of this in my blog or websites when I search, so I’m publishing it here, a mere five years later.
This morning I experimented with some Google searches which can reveal information on public sites.
Inspired by some posts from @Random_Robbie on Twitter
These are now know as Google Dorks.