If testing is easy, you're doing it wrong.

Now is the time for me to elaborate on what I want to say. I still believe some will disagree with me, but this could lead to some interesting discussions.

Testing is challenging.

As we all know, testing is never complete. It is one of the testing principles that exhaustive testing is not possible.

I work as a hybris ecommerce tester, and there are always additional test scopes you could run. This means that you must always select an enormous number of tests to run. Many of them are easy to skip, but if you have a ton of good test ideas and test scenarios, it's hard to skip any test. At the very least, I often find it difficult to choose which ones to skip.

Things will change after you are completely satisfied with your test coverage and you learn about new things or issues, your surroundings will change, and your tests may no longer be the best.

Also, which tests should be repeated? How much of an impact should it have on the business? And, in my experience, that cost is always difficult.

Because testers are human, they make mistakes .

It's surprising if you never make mistakes. Mistakes can be minor or major, and they are sometimes recognized and sometimes not. Mistakes can sometimes lead us to important information. There are numerous reasons for errors, but one of them is that we are dealing with complex issues, both in terms of technology and people. We don't know everything ahead of time (if we did, testing would be unnecessary), and learning is personal and sometimes "wrong," but always beneficial.

Bugs we've missed frequently fall into the "I didn't know about that" or "I missed that scenario" categories. If something is obvious, not learning about it could be considered a mistake, but there are so many things that could be interesting that it is difficult to know in advance.

We must also be wary of an environment in which making mistakes is frowned upon, as this can lead to situations in which people are afraid to try anything new, and productivity, creativity, well-being, and other benefits vanish.

At the same time, it is humanity, learning, mistakes, and creativity that make software testing important and fascinating!

Conclusion

• This is why I employ the "Thank God it's not easy" .
• If it feels too simple, I haven't learned enough.

Of course, this isn't unique to testing; it probably applies to most areas that deal with complexity and ambiguity.

I know my thoughts are also not novel but maybe this article will help you to understand more about testing and testers.