Development vs. Testing, or where to go to the graduate of the MVF

    There is an opinion among a certain part of IT specialists that software development and testing should be considered as antagonistic processes. Indeed, writing source code, design development, etc. - These are creative processes, while testing is always destructive. Against the background of the specifics of their activity, various workers and sometimes personal conflicts constantly arise between the specialists of the two areas. Therefore, development and testing teams often confront each other, and employees are divided into “strangers” and “friends”. What kind of camp should beginner IT join? We will try to analyze both directions and answer this question.

    It is believed that development is more intelligent, creative, and as a result, a more paid area than testing. This is one of the well-known myths regarding the profession of a tester and nothing more than the subjective opinion of individual individuals. From an objective point of view, each specialist performs his own unique stack of tasks. For a programmer, this is code writing, interface design, unit testing, studying and applying optimal designs and algorithms, as well as matching templates. The tester, however, needs knowledge of the subject area, analogues of the system being implemented on the market, knowledge of typical errors of such systems, in addition, for the design and execution of tests, knowledge of test design methods is also required, and in the case of automation, it becomes necessary to understand modern auto-testing tools,

    Another, equally common, myth is that testing is more routine work. In fact, it all depends on the specific project and the specific role on it. In the testing process, there really arises the need to conduct a regression, which is not famous for its diversity. At the same time, the tester can take part in creating a new automation framework, or engage in manual testing of new functionality. The same principle is true for any developer: depending on the role, the specialist can support existing components or take part in creating new ones.

    Many are interested in the issue of remuneration, namely, the difference in the salaries of the developer and tester. At the stage of origin of the QA region, perhaps this difference was not in favor of the latter. Nowadays, the delta is almost leveled, and in some cases exceeds the cost of the programmer’s services - it all depends on the project, the person’s experience, his skills and the significance of these skills for the team.

    And finally, thanks to the myths and opinions described above, many young specialists who do not have experience in development, but, nevertheless, consider this area to be “imbalanced,” try by hook or by crook to get the position of junior or regular software developer. Including, using the position of the tester as a kind of springboard for further transition. The fun part in this case is that most of these applicants subsequently decide to connect their lives with QA.

    So, to summarize: most stereotypes regarding the profession of a tester have no objective basis. At the moment, both directions are equal. A creative, ambitious person is able to prove himself in both areas. It cannot be said unequivocally that the activity in one of them is clearly more interesting than in the other, as it cannot be said otherwise. Before making a decision, it is necessary to familiarize yourself with specific responsibilities in detail, and it is better to work for some time both as a tester and as a developer. Only then can a person determine with certainty which path is closer to him. Moreover, this will avoid the spread of well-known misconceptions and increase the overall professionalism of the employee - understanding the tasks of both departments will reduce the likelihood of conflicts and misunderstandings in the team.

    In conclusion, I would like to note that, of course, testing and development are two integral parts of one process. Without one, one way or another, there will be no other. Therefore, no matter what position or role you are in, always respect the work of your colleagues with respect.

    Also popular now: