He he. it’s a bit of a loaded question. As someone who has not been a tester that long, but have been a coder for long enough I have already a firm opinion on how assumptions around a product work.
And no I’m not talking about the tired old “build me a swing” meme - I mean this picture was a meme long before memes even existed.
…so I’m going to suggest testers look at the “entire product” more often than at just one piece, because models, integrations, environments, black, white and boundary analysis, performance, and expectations etc. all are tools in a box that inform us of the quality of a product. This last few weeks I have had a few assumptions of my own shattered. Due entirely to release pressures the testing squad have pushed back on testing work around new features and prioritized the testing of bugfixes and any committed to deadlines. A side effect of that was that devs have to do more of their own testing than usual. And this tweet by someone I have a crush on although I’m sure she is unaware of it, was my regular reminder.
The job of every tester is to spot assumptions in the wild, collect and corral them and then design useful experiments that prove or disprove the valuable ones. What tool we decide to use for that is always going to be context specific and rely on experience. Always assume that you can learn a new thing every day.