Blog Posts

Are you recruiting people, or are you recruiting to fulfil a role? Here are tips and notes about recruiting and interviewing.

The Triangle Problem is a ‘classic’ from Software Testing, described in many books and training courses. This post describes the problem, links to some applications you can use to practice on and describes some nuances around the testing.

TLDR: Every time we test something we are testing from models. Modelling is a key skill for Software Testers. Errors cannot be identified without a model to compare them. Quality Control cannot be conducted without a model.

This episode covers the Test Automation Pyramid, created by Mike Cohn in 2008-2009 in the book “Succeeding With Agile”. We will go beyond the diagram and look at the model that supports it. Then deep dive into the model to explore it’s meaning in relation to Automated Execution Coverage, not Testing.

The most common Testing Entities that I’ve encountered over the years are: Test Condition, Test Scenario, Test Case, Test Script. In my Testing I pretty much now have: Test Idea, Test Log (Execution Log). Is there any value in the original Testing Entities? There might be if we view them as logical concepts, but not really as physical artifacts.

Top 3 Phrases that should carry trigger warnings for the Test Community: Manual Testing, Test Automation, Quality Assurance. In this episode I’m going to talk about Manual Testing. And I’m going to talk about what we might want to say instead of “Manual Testing”.

TLDR; There is no need to practice testing on public websites and annoy the owners. There are lots of applications to use to practice.

TLDR; Modelling is a fundamental skill for Software Testers. Applying modelling to Software Testing itself allows us to communicate our testing in simple terms and we can explore how concepts build on, and relate to, each other.

TLDR; Browser dev tools change frequently. I can through the tooling from left to right and explore them to learn the capabilities.

This post provides a high level summary of the Chrome Dev Tools as they were in September 2022.

Manual QA is dead. Companies are getting rid of their QA teams. Quality Control performed manually is phasing out of style. What can we do instead? Become coaches, assistants or advisors? We could become developers? Or we could be better testers. QA and Quality Control is not Testing. This might be how people learn.