Yazılım Test Mühendisi

Giriş
Bazı firmalarda Yazılım Kalite Güvence Mühendisi aynı zaman Yazılım Test Mühendisi vazifesini de görür.

Yaş
Hem testçi hem de yazılımcı için belli bir yaşa kadar bu iş yapılır diyen yazılar ve konuşmalar var. Bu tür konuşmalar kesinlikle doğru değil.

An IT specialist is such a strange profession that in his youth an employee is much more worth than in his old age. I am not joking. The programmer is able to withstand two technology changes, and these changes are every four to five years. And then he has to go to other things. Become a consultant, go to work with a client, become a systems architect. It's like with footballers. At some point, they have to stop playing.

Hataların Yerini Yazılım Test Mühendisi mi Bulmalı Kodlayan Kişi mi ?
Hataların tam olarak kimin bulması gerektiği her zaman tartışılan bir konu. Konuyu hem testçi hem de kodlayan/geliştirici açısından irdeleyen bir açıklama şöyle

There is no clear dividing line between the bug isolation and reporting that the tester does and the debugging that the programmer does. In most organizations, there's plenty of room for the testers to put more effort into bug isolation. On the other hand, there may also be reasons to have the testers report the first symptom they see and then move on.

Here are some factors in favor of having testers put significant effort into isolating the bugs they report:

• Testers may be more motivated than the programmers to show that the bug has a real impact and should be fixed.
• Because they spend more time on bug reporting than programmers, the testers may be better as bug isolation than the programmers.
• The information that the tester learns about the bug can be put into immediate use for further testing.
• Testers may have access to more resources, such as staff and lab equipment, than the programmers.

However, there are also factors that could indicate that it's best to put most of the weight of bug isolation on the programmers:

• The testers may not be highly skilled or experienced, so they may not be adept at bug isolation.
• Testers might put significant effort into isolating a bug that turns out to be a low priority for fixing.
• Testing resources may be more constrained than development resources.
• It might be more productive to use knowledge of the code to zoom in on the problem.
• Having the testers do significant bug isolation makes their somewhat unpredictable project schedule even more fluid, because it's hard to predict how many bugs will be found and how hard they are to characterize. Of course, the programmers have the same problem if we shift the work to them instead.