Software Testing and Development Blog Posts

TLDR; Focus on the reason behind the measurement. Use trends in measurement to help adjust strategy.

TLDR; Claims, and Expectations can be used as a high level description of Software Testing. Given a set of claims, check if claims are met. Create a model based on expectaions, then use and evaluate expectations. Further explore to identify scenarios where claims fall apart and expectations are unsatisfied.

TLDR; Given a model, we can apply a technique. Given a model we can apply many techniques. Techniques are a way of extracting a coverage model from an input model

TLDR; Are you getting the results you want from testing? If not, change how you test as part of the development process. Don’t change the role definition of “Tester”.

TLDR; Plan, Practice and Communicate as efficiently, clearly, and concisely as possible.

TLDR; What does Software Developer actually mean? I don’t think it is synonymous with Programmer I think it refers to someone who can do most of the activities associated with creating, releaseing and selling software.

TLDR; Reading is fine. But at some point we have to put it into action. Identify an appropriate “thing”, Try it in a controlled environment, Apply it in the real world.

In this podcast I discuss test automation biases and how to avoid them.

Adopting a personal approach to Testing led me to adopt an exploratory approach to Testing, one driven by unique models, decisions, skills and sources of knowledge.

TLDR; Kerry McKeever explained and demonstrated his AG Grid automation plugin for Cypress, showing where to find the code and how to create custom commands for cypress.