Subscribe to the full blog feed using RSS
TLDR; Variation in testing often leds us to test data, flows and environments. We can increase the chance that we learn something relevant by reading more blogs, watching YouTube and attending conferences. We can also trigger insights, that we ourselves have gained, by reading meaning into unrelated text, content or koans.
TLDR; More code to study, conference slides to read, useful tools and more…
TLDR; New code to study, some apps to test. And some blog posts…
TLDR; LEAPWORK tool helps automate web applications and APIs using graphical building blocks instead of a programming language
TLDR; An example of modelling the application flow of a simple functionality. Modelling helps think through coverage and test ideas and think about what next for your testing.
I chose the very simple I Feel Lucky functionality on Google to use as an example application for modelling to support exploratory testing. I recorded the modelling session and explained my thought processes as I went.
TLDR; A new course. And some blog posts…
I was asked a question over email, and I’m paraphrasing the essence as, “given our project issues what tool can we use to automatically pull out all this data and automate the app to let us test it properly?”.
Unfortunately most of the time, when I’m asked this, the answer isn’t what people want to hear.
TLDR; The formal api documentation specifications ecosystems have tools that can help create documentation more easily and use the documentation to automatically validate e.g. Dredd, Swagger and StopLight
I’m working on an API for The Pulper, and I want to write documentation in a formal spec and use tools to validate it. Sounds Easy.
TLDR; Two online events, one workshop, a podcast, and a tonne of Patreon content.
TLDR; A simple link checker running from a snippet or console has some secondary advantages like jumping to the links and showing CSP and CORB errors