admin
Feb 2,2010
In: Articles

Tester

Definition

Who is the tester? In fact – a person in a professional whose responsibilities include the detection, localization and tracking of various errors in the program, a description of themselves, as well as steps for them to play. In practice, this is the man who, together with the developer provides a quality program. We believe that taken as a tester "gospriemka" not worth it. But do not consider him as "assistant programmer." The tester is likely a link between the developer and user. This is a specialist who can examine the problem from a user perspective, and discuss it with the developer in the language of the programmer.

You should not confuse a tester and a beta tester. The first – a professional, performing their work and receive a salary. The second – usually a user program, which the company prevlekaet for "running" is almost finished software. Payment for his work in this case is likely to be able to "feel" the program even before it officially appears in other users, as well as the opportunity to purchase the official version at a lower price. However, this does not detract from Denote beta. Without this step the final product can never be "unclaimed."

Quality tester

What qualities of a tester:

First of all – of observation. A practitioner of testing should notice the slightest irregularities in the test program during the test.
Pedantry. Any test should be conducted thoroughly and that not once.
Perseverance. Testing of any software including and games is no easy task. It is not uncommon tester spends on the computer a lot more time than the developer. Gluck is necessary not only to find and describe, but double-check, after it will be corrected by the developer.
Persistence. It is not uncommon tester has to defend his case by proving the existence of a bug found, which is not played on a computer programmer.
Tact. Software is always part of the programmer, it develops. Do you love when you show your mistakes?
Communication skills. Tester does not exist "in itself". Will it work in a team of other testers, or only with the developer – no communication he can not do.
Love to work. Trite? Perhaps, but the fact remains. If you are not interested, you will not last long.
Desire to learn. Technology has not even come, but rather a run forward. To test, you need to know all about those products work with which you have in the testing process.

What you should know a tester?

The tester must be familiar with basic concepts on the basis of the task, ie proficient in terminology.
The tester must know the operating system, which is tested at least at the level of "advanced" user.
The tester should know all the applications installed on your computer.
The tester should become familiar with the program under test (here, a lot depends on the workflow between them and the developer).
Preferably, the tester should have at least basic knowledge in programming language, which developed the program under test.
The tester should be able to use special software for testing, including automated.
The tester should be able to write, read, and sometimes draw:).
What should be the tester?

What should be the tester?

First of all – the computer. While not one but several: a separate test (called a test computer), and separately – to the rest (eg, database management, the documentation, writing plans, getting mail, etc.) It is desirable in the event of an office you have a computer at home. Not necessarily ultra-powerful, but enough to work even with the "office" software.
Workplace. Your work demands attention. If you ever go by, distracting, do not give a focus, you simply will cover the project.
Communication (telephone, e-mail, etc.).
Desire to work. Not in any way, 24 hours a day, 7 days a week – goes wrong!
Wages. You are a beginner? Your professionalism is in your hands! You will not eat the same air, and feed your family with promises of a lifetime?

Advice

Tester:

Be careful. Before documenting a bug, make sure it is really a bug, but not your mistake. As the saying goes: "Seven times measure …"
Do not quarrel with the developer. Nobody likes to "curse" of his work, or "point" to make mistakes. In no event do not work together with the developer, who is your friend, brother, husband / wife, friend or just a man, its good relations with whom you cherish;
Play bug describes the steps as detailed as possible. The developer is not a psychic. Remember that and you still do not have time to go back to your same description;
do not work for wear. It is not only undermine your health, but at the critical moment (eg, delivery of the project) let you down. Who needs a tester who is sick all the time?
do not take time off from work. Want to make you not trust?
do not overestimate its importance, but do not underestimate her. You are the one who you are. No more, no less;
insist on the provision of timely and complete documentation. This will provide you with the normal operation and enhance its effectiveness;
do not ask too much. If you do not give the new equipment, and work on what you have, but remember this when drawing up a preliminary plan for testing and development of its timing;
Do not throw away or sell old parts. They may still need you in the testing process;
Keep yourself in their hands. Hard glitch – not a reason to yell child. Your family – a friend, not foe!
Remember: enthusiasm – well, but one passion can not eat!

Developer:

Tester is not an enemy but a friend. He also has a family and caring. Respect his work!
Do not quarrel with the tester. He, too, and people can make mistakes. The project is a general!
do not take the tester as the person who just does nothing but find fault with your child. It is from this will only get better. He, as well as you seek to project ended successfully and on time.

Manager:

do not ride the relationship between the developer and tester. Do not let the conflict;
do not put the developer in obedience to the tester, or vice versa. These are two absolutely equal team member;
provide the necessary equipment is not only the developer, but the tester. Do not skimp! Remember that the quality of the equipment depends on the test result, and hence the success of the project;
Ensure the tester normal operating conditions (room, desk, chair, lighting, telephone, etc.);
if resources permit, and there is a need, provide a tester normal conditions of life and relationship with him;
without prejudice to the tester in wages. Remember that it is better to start small and gradually and continually improve the pay for work than to pay a large sum at once with no prospects of growth.

Of course, that everything written here – a "perfect" version, which, in our opinion should be sought. Unfortunately, real life is not so smooth.