Explore all our content
Dive into our back catalogue of content. With over 2000 pieces of content to digest, there will definitely be some software testing content of interest to you.
Searching...
We've probably all experienced "that look" that people give you when something goes wrong.
I've lost count of how many times I hear a random person say, "Why doesn't this thing just work!" It's tiring. Yet I also have an internal wry smile thinking that we testers will continue to improve the world of apps. AI whatever, we'll be alright. 😉 Happy World Testers Day!
A lot of the time "testing in production" has a negative connotation and meaning. But once you dig deeper into the source of the fear you will find that different people mean different things by it.
Some people, when they say it, mean: “I ONLY test in production”.
Others mean: “I test before it and I ALSO test in production”.
You want to know if your production is up, running, and happy, aren’t you? This is achieved by testing! It could be performed “actively” by manual exploration or “UI end-to-end” automated smoke tests. Or “passively” by looking at the monitoring dashboards.
But you need to do it and there is nothing wrong with it. :)
Stepping away from the testing community is cool, particularly if you're just not in the place to stay connected and involved all the time. It's also healthy to take a break when you can, even if you're fully committed to being a community member. This meme represents that feeling of returning to a community after time away or time off. A lot can change and it can feel odd. It takes effort to come back yet there's that realisation that it's worth it!
Must have, hot off the press Mnemonic that everyone must know and apply to their software testing 🔥
It's very easy to be critical, raise bugs and give feedback that doesn't help a team move forward. Always ask yourself if your work will be of value and good use of time, because time is money.
This is a phrase I've come to use a lot to describe my frustration with so much of the testing community's obsession with paperwork and test artifacts--test strategy documents, test plans, test cases, etc. or constantly referring to "test" only as a noun (e.g. "writing tests"), and far too little emphasis placed on actually _testing_, doing the work, exploring, and finding problems.
