DEV Community

Gaurav Singh
Gaurav Singh

Posted on • Originally published at automationhacks.io on

๐Ÿ“› Common terminology misses in software testing

Image showing green tick and a red circle
Created by microsoft copilot using DALL.E 3

I posted about this topic on LinkedIn and saw a lot of engagement. Somehow I have this eerie feeling that Iโ€™ll be pointing people to this blog in the future as well ๐Ÿ”ฎ

  1. Itโ€™s not automation testing, itโ€™s automated testing - We are not testing automation, we are automating tests
  2. Itโ€™s not QA Automation, itโ€™s just Test automation or better Automation In Testing (AIT) - we cannot fully automate quality assurance, it is a broad term and some activities will require human intuition, we can automate tests to give faster feedback at scale.
  3. Itโ€™s not a QA Automation engineer , call them SDET or Test engineer please, and yes people with these titles both write automated tests but there are differences, read this
  4. QA Engineer is not the same as SDET , again there is a difference ๐Ÿ˜‰ - read blog in point 3 for more details
  5. Flaky tests are not the same as broken tests, there is a difference ๐Ÿ˜‰ - Broken tests are nice as they fail all the time, but flaky tests? not so much, sometimes they pass, sometimes they fail, but they always point to a nice problem underneath to debug, donโ€™t ignore them, and donโ€™t retry them 5 times.
  6. Assertions and checks are mostly the same! I rest my case!
  7. Quality engineering is loosely the same as QA Engineering as a term to refer to the organization - dropping assurance does not make much difference. Leadership does implicit conversion anyway and applies their old biases. Calling it Test engineering is more explicit
  8. QA is a process, itโ€™s not an engineer - Would you refer a person with something abstract? Probably not. Calling them testers is much better and more explicit. ๐Ÿ™
  9. 100% automation , really? - your energy is much better focussed on ROI (return on investment) driven automation. The Pareto principle exists for a reason. Chasing vanity metrics just leads to unnecessary suboptimal waste

Your mileage may vary. We can refer to the same thing with different labels and thatโ€™s completely okay

Did I just stir up a hornetโ€™s nest? ๐Ÿซฃ

Iโ€™ve learned to not care about these much but occasionally push some buttons and I prefer some over the other. I thought Iโ€™d just put it out there.

| Thanks for the time you spent reading this ๐Ÿ™Œ. If you found this post helpful, please subscribe to the substack newsletter and follow my YouTube channel ( @automationhacks ) for more such insights in Software Testing and Automation. Until next time ๐Ÿ‘‹, Happy Testing ๐Ÿ•ต๐Ÿป and Learning! ๐ŸŒฑ | Newsletter | YouTube | Blog | LinkedIn | Twitter. |

Top comments (0)