Software Testing and Development Blog Posts
Subscribe to the full blog feed using RSS
Subscribe to the full blog feed using RSS
A webinar in partnership with QA Symphony on 28th June 2016. What is Risk? How do we use it to help us test? What are the risk of testing in certain ways? What are the risks of not testing with a technical focus and exploratory mindset?
TLDR; I try to write tests at an appropriate semantic level so I never need to create dependencies between @Test methods, I re-use abstraction calls instead of dependencies between @Test methods.
May 2016 in London, at the National Software Testing Conference 2016, I presented a talk entitled “The Art of Questioning to improve Testing, Agile, and Automating”
With only 25 minutes to present, I had to make very sure I was conscious of the main points I was trying to drive home. This was always going to be a topic overview, but I wanted some very obvious and actionable insights for attendees. And hopefully spur them on to future research.
We don’t have to build full applications to create test tools. Sometimes we write throwaway tests.
TLDR; subscribe to master commits on github with
/commits/master.atom
I wrote an article for the Testing Circus April 2016 issue. With the controversial and thought provoking title of “Join the Anti-“Test Automation” Brigade”. It has substance and is not just click bait.
Who doesn’t like looking at the innards of a web page and fiddling with it?
With most libraries you use to automate your work, you have to code workarounds. Here is a strategy for being informed when the workaround is no longer required.
TEST Magazine asked me to step in and write a quick answer to the question “As more organisations transition to an agile environment, how will the testers role be redefined?”.
An explanation of the Java Main method, and why we don’t really need it when automating.