I like programming. By chance, I became a software tester, although I was interviewed by a developer. I've been testing for 1.5 years, it seems tired .. I want to program and go into the category of developers. After work, there is little strength to invent and program something.

The result is that due to the work of the tester there is not enough incentive and time to go to programmers

Tell me, please, it seems to me, I am missing something

Closed due to the fact that it is necessary to reformulate the question so that it is possible to give an objectively correct answer to the participants of Athari , ixSci , fori1ton , pavlofff , AntonioK 12 May '15 at 6:43 .

The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • one good tester costs 5 programmers. - zb '10
  • @eicto 5 ordinary programmers (coders), but 1 good tester = 1 good programmer - IVsevolod
  • one
    But for personally for the vehicle, for sure there is. @ alhimic37, everything is simple. If you don’t like the work, you have to change it (or just tell the boss about it). - avp
  • @avp, good advice - alhimic37
  • @eicto, I agree with you - alhimic37

2 answers 2

A good tester (what is called Software Engineer In Test ) is, first of all, a first-class programmer. I don’t know exactly how your workflow is built, but tests are sometimes more difficult to develop than a test application. Want to program - start, for example, with the automation of your entire routine at work. Or offer your team help in writing unit- and integration-tests.

  • Valuable advice, @ Kotik_hokhet_kushat, thanks :) - alhimic37

@ alhimic37

I, too, like you are a software tester. It was arranged by the developer, but due to the fact that the guys in the team write much faster than me, I turned into a tester. Analyzing why everything has come to the conclusion that I’m focusing too much on questions like “What if I submit here ...?”. At that time, the guys in the team, as a rule, are not soared and just solve the problem.

I mean that you have already answered and answered correctly. "A good tester is first and foremost a good programmer." This is not possible to disagree. And if you look at software testing and quality assurance in general, you can see that the tester also has programming! Examples: Automation of testing, automation of analysis of output reports after programs, generation of test cases and test data.

The difference between a tester and a programmer is that a tester writes a program for people who are keen to break the product code being developed. This program for people is a set of test scenarios. Example: 1) Start the program 2) Open the menu 3) Seeing the item ... 4) Press 5) You should see "...." otherwise BAG.

Yes, and the process of playing the bug is a very exciting process. To make the bug turn from Heisenbag into an elementary sequence of actions leading to a bug is sometimes more fun than debugging the program itself. Yes, and the developer after such a wording bug already debugging less, because for him have done quite a lot of work.

Tester: this is not bad, it is an honor !!!