Industry Carelessness

-
Looking through the LinkedIn feed I see a horrible thing. I think we can call it "Industry Carelessness". I see lots of posts of the kind:
  • Automating testing using XXXXium
  • Digital transformation using microservices architecture (please download our brochure)
  • We will transform your business, here's how
And so on. This is very disturbing. It is like "we don't know what the problem you have (if any) but we have a solution already!" Moreover, I worked for a company whose whole business model was like that, which was delivering what it had in place instead of what was necessary.

I interviewed employees who did not know where we were but already knew where we should go and how do we go there.

"Ok, we shall do this and that".
"Hold on a second, don't you want to know what we already do and what results we get?
"Not necessary, the industry goes into that direction so let's do thing 'right'"

And even worse, I was once the one who did not understand what was really happening but was eager to suggest disruptive measures to "fix things". It was a great experience - on the job interview where I was asked about the "ideal test automation process" and I described Pretotyping, BDD, TDD, and testing in production.

"We will get awesome time to market" - I bragged happily
"Yes. You are right. The thing is that time to market is not actually our concern... Our concern is that we have lots of issues in production and that badly affects our business" - calmly said the guy who was interviewing me
"Oh, shi~"

So chances are that my treatment would be worse than the disease. Or, more accurate, they were for the wrong disease.

So hereby I want to share a dream with you.
I have a dream where companies care about their customers, who tell "We don't know the solution yet, but promise to understand your problem and do our best to solve it. If we fail we will suggest another company who could do this better".
I have a dream where employees first understand what is wrong before "fixing" it, and me being among them (so I hope not to repeat this mistake again).
I have a dream where my feed full of thought-provoking posts, for instance, "Ok, that was the problem, we tried this and here how it is worked - let's discuss".
I have a dream where we and companies care.

Say no to Industry Carelessness.

Comments

Post a Comment

Popular posts from this blog

Test automation framework - do I need it at all?

-
Image
While there're lots of information published on the internet about how one should develop/buy a Test Automation solution, there's an elephant in the room - which is the fundamental question "Do I need to do it at all?". That is a good question. While I think that there’re some legitimate contexts where product/project/team can benefit from having a sophisticated test automation solution/framework, my general rule of thumb is “If you need a framework - you do it wrong” . There’re at least several decent papers showing the benefit of unit-testing ([1],[2], [3]), while I could not find any research proving that system level tests could bring better results. Please let me know if you can prove me wrong. There’s at least one half-scientific paper showing the benefits of unit tests in comparison to integration/system level tests [4] There’s a good paper bringing a notion of running/writing and maintaining test vs. the benefit of having/running it at...
Read more

Efficient test automation - Secret #1 | Test Club

-
Image
It seems everyone talks about efficient test automation, but not so many people have actually seen it! To cover this I decided to make several videos regarding the secrets of efficient test automation. Today we will talk about the first (and, arguably, the main) secret - realistic expectations. Very often, test automation projects or initiatives are started with the following unrealistic expectations: "Test automation will replace 'manual' testing" "Test automation will provide fast results and benefits" "Test automation efficiency depends solely on test automation engineers" Unfortunately, all those expectations are not realistic! Watch the video to know more!
Read more

An alternative to ubiquitous UI-level checking - Subcutaneous tests

-
Image
Let's assume a hypothetical situation - you were assigned to a project to help with the "test automation" initiative. You have a huge "test plan" as an input, containing hundreds (if not thousands) of "test cases" and you need to do something about it, quick. Problem statement Your first urge (if it is a Web application) may be to write some UI-level automated checks using tools like, you know, Selenium. In fact, there's a huge demand for such "Selenium test automators" in the industry these days. But please, please, don't do this. There're lots of things which make UI-level automated checking the least desirable approach: UI-level automated checks will be slow. There's just no way to avoid it. You can parallel them or do some other tweaks to speed them up somehow, but they still will be slow. UI-level automated checks will be flaky. Partly - because they're slow. Partly because Web browser and UI interface w...
Read more