Note: This blog post was originally published as a guest blog post on the LogiGear Blog under the name Continuous Quality – Ethical aspects of software testing Daily, we are pushing the boundaries of how fast we can deliver software. Delivering something new, better, faster than our competition can mean incredible payoff and we are constantly being asked to cut costs and deliver more, faster, cheaper. But then suddenly you wake up to 189 dead…

I recently had the pleasure of attending TestBash Germany both as a workshop fascilitator and as a part of a speaker panel. On the panel we got to answer a wide range of question and I spoke a bit about teaching and mentoring junior testers. After the panel I was approached by a wonderful woman who asked me the fantastic question: "What (non-testing) skill/area is most important to learn as a tester?". My short answer…

So my recent Power Hour at Ministry of Testing got me thinking. To start: I'm sorry, tomorrow-morning-me, apparently I had to write this now, while on the rush of that experience. Why am I feeling this rush? From a Q&A? Well. I'm doing a workshop about security testing and OWASP Juice Shop this fall and I've been worrying about it. - Maybe it's too easy and scripted? - Will people learn anything? - What if…

There has been a lot ofdiscussion, heated and calm, about the concept of testing. What it is. What it is not. Arguments about real testing vs. what a lot of people imagine when they hear the word. Twitter and blog posts talking about “real testing”, “the future of test”, “no testing” and so on, seemingly endlessly. To be honest, I’ve had a hard time grasping a lot of it and some distinctions don’t make sense…