5 Confessions of a Software Test Engineer

Dmitry Yarygin
Software Testing: Break and Improve
4 min readOct 17, 2021

--

Photo by Christina @ wocintechchat.com on Unsplash

I’ve been a Software Test Engineer for over a decade. I’ve worked with small and large teams and over time I’ve accumulated many things that I love about this area of work.

Working with talented people and helping create big products is among those. There is also a reality. It’s not good or bad, it’s just how things are happening when you are working as a Software QA Engineer.

This is a list of things that I’m personally aware of and those are my recommendations on how to make sure the software development process is smooth.

No, this feature was not yet tested

No matter how many times I’ve heard that the feature was already tested by the developer and only needs minor testing — this was either not true or partially true.

And I absolutely expect that. The developers only have tested a small part of the feature on their local environment, which means:

  • A local database
  • Rapid fast back-end, because it’s also running on local-host
  • Emulator instead of a real device (in case of Mobile testing)
  • Only one operating system and browser (in case of Web testing)
  • Only one type of the account
  • Lack of knowledge of

--

--

Dmitry Yarygin
Software Testing: Break and Improve

Nomad lifestyle writer. Passionate about breaking software— QA Engineer. My Travel & Tech YouTube channel: https://www.youtube.com/c/nomadicdmitry