ІТ-workers debate whether a developer should test their product independently
Team Lead/Python developer Olena Kuznetsova expressed the opinion that developers should also be seriously involved in the testing process of their own product.
Team Lead/Python developer Olena Kuznetsova expressed the opinion that developers should also be seriously involved in the testing process of their own product.
«A developer should test their product independently. And a product/business analyst should also be involved in this process when a business feature is accepted. The testing department is not a backstabber who will catch all the bugs for developers, but people who catch some strange things, depending on their qualifications, configure test automation, help determine the quality of the product in general, and give an outside perspective,» she expressed her view in a post on LinkedIn.
ІТ-worker believes that if there is a testing department, it’s good, but if there isn’t one, it shouldn’t change anything particularly in the work of the person who writes the code.
«Yes, it seems like extra time, but it will be justified by understanding what a person is doing and why, by a closer connection with the project. This gives more chances for initiative on the part of developers. It gives more dopamine from understanding that you have done something tangible. It gives strong ties between departments, mutual respect. The testing department does not feel like service personnel (they are not given functionality that clearly does not work, as if mocking them). The development department is not bombarded with bugs, and they are not enemies (it is much easier to hate the person who pointed out your mistake to you, even if it is objectively their job),» Olena Kuznetsova justified her position.
Also, according to the author of the post, this speeds up the feedback cycle, because, in her opinion, it is much easier to work when you don’t wait for the code to be taken for testing, if, most likely, «they won’t find anything critical and urgent.»
Other representatives of the IT sector also expressed their views on this situation.
«I completely agree. Sometimes the point here is that the developer believes that a bug in production is the tester’s fault. Well, like, the testers themselves should be to blame for not testing properly. In other words, the developer shares or even transfers responsibility for the error to the tester. In fact, in my opinion, the presence or absence of a tester should not change anything for the developer. A bug is a bug, regardless of whether it got into production or not,» says IT entrepreneur Oleg Frolov .
Team Lead and Product Engineer Yevhen Turovets believes this is correct, but somewhat utopian.
«I can only agree with all this and state that it is very utopian… Perhaps the situation on the market will change something, but it is very difficult to get a good pretest from a developer… I won’t lie, I myself sometimes submit a feature that is not super-tested because I simply don’t have time or it is already driving me crazy! The best thing for me here is a retest the next day, when you are not tired from the day yet!», he shared his own experience.
Senior frontend developer Rustam M. completely agrees that the functionality should be tested by the developer himself.
«He must be almost certain that there are no bugs, at least those that are directly related to the task being performed. This approach will save a lot of time and nerves for the developer himself, he will not have to rush between tasks and lose concentration,» he says.
But in the case of a more complex scenario, according to the IT expert, a tester comes into play.
«He can devote more time to finding problems, and most importantly, it is a guarantee of quality before deployment. Therefore, everything that gets into production is already QA’s fault. For QA, it should be a challenge to find something, and for the developer, it is pleasant if they don’t find it. There will be no „passion“, there will be no quality result, but there will be a sluggish pushing of the task back and forth,» concludes Rustam M.
As dev.ua wrote, automation QA Engineer Olga Markova shared a selection of tools that will help testers create accessible websites that should be suitable for use by people with additional needs, including those with visual, hearing, cognitive, or physical disabilities.
«It was different, but nothing like this.» Tester tells how employer canceled interview at the last minute
«It was different, but nothing like this.» Tester tells how employer canceled interview at the last minute
QA Engineer has compiled a selection of Ukrainian YouTube channels about IT, testing and development
QA Engineer has compiled a selection of Ukrainian YouTube channels about IT, testing and development
«While you’re at it, someone who’s ready to work 24/7 will take your dream job.» How to get into IT when you’re 40 and times are tough: tips from a developer
«While you’re at it, someone who’s ready to work 24/7 will take your dream job.» How to get into IT when you’re 40 and times are tough: tips from a developer
Read the country’s main IT news in our Telegram
Read the country’s main IT news in our Telegram
