Subscribe to the full blog feed using RSS
TLDR; Imagine never having to worry about saying “Verification” when you meant “Validation”. Well you can. Write down what the V-words imply, and then use those sentences you wrote down instead.
I’ve been in meetings where people have argued about the words “Verification” and “Validation”. For some reason these words have a high weighting of importance in “The World of Software Testing”.
I have the personal issue that I forget which one is “meeting requirements” and which one is “meeting needs” and have to reverse engineer the words every time I need to use or interpret them.
I’m not the only one, because often I see the questions: “Am I building the product right?” (Verification), and “Am I building the right product?” (Validation).
And I asked myself, “What if I don’t use the words verification and validation?”
The new “Evil Tester Show” episode covers the topic of Workarounds.
Have you ever used a workaround to get something done?
You betcha. In this show I describe some examples and how important they have been in my testing and my career. And some of the risks you face when you use them.
I have created a list of the Micro Courses in the EvilTester Patreon site.
TLDR: Do you ever ask yourself rhetorical questions? If so, try and answer them by building assumptions. Then investigate your assumptions.
Do you ask yourself rhetorical questions?
I suspect most people do.
Leaving them unanswered means not following up on a opportunity for learning that your brain has put in front of you.
TLDR: Rather than discuss ROI in depth, I want to explore how to evaluate ROI for yourself, so I provide some questions as an exercise e.g. “Why do you use ROI?”, “What do you gain?”, “What do you lose?”, etc.
I am often asked about ROI. And I wrote a parody answer. In this post I explore initial beliefs and then questions to explore and expand my model of ROI.
TLDR: If you want to invest in yourself, we have books and courses and a patreon page
Finding testing too expensive?
Trying to replace your testers by Automating Testing?
You’re doing it wrong.
Tool vendors want to sell you tools to automate your testing and make testing cheaper - but here’s what they don’t tell you.
I have been using
TLDR: clean recon - using the app to provide knowledge about the app
Using The Pulper v 1.2 I recorded a live recon session to try and create an example of note taking, model building, risk identification and next action identification.
You can repeat the exercise for yourself and see how you get on.
For the first time, in a long time, I’ve had to bypass WebDriver
In this post I’ll explain why, and look at the pros and cons of doing so.
TLDR: github.com/eviltester/testingapp new version has more apps
To help you practice your testing I have The Evil Tester’s Compendium of Testing Apps.
One download - lots of apps to practice testing on.