Who are game testers and what do they do, what do you need to learn this and what knowledge?

Question

Programming languages

Generally.
For a long time I thought about who I want to work. And since I spend a lot of time in games, I had an insight.
I want to learn more about testing and how it goes, and what you need to learn for this, what programming languages, etc.
Thank you all.

Answer 1

A game tester is an ordinary tester who was able to get a job in a company that develops games.
You need to learn the same as all other testers, namely:
1. Be able to work. Not to play, but to work. If they say instead of "play" to check tons of text in text dialogs for localization - it means to check tons of text, perhaps even without starting the game at all.
2. Be able to organize yourself for long monotonous work. Perhaps the same bug will occur many times, and everything needs to be rechecked.
3. Write correctly in Russian and English (MINIMUM intermediate) to fill in the fields when opening a bug.
4. Adequate Computer Essentials knowledge. You don't have to be a sysadmin, but what's the difference between a bit and a boolean, how to run a .jar, what is a console - quite helpful.
5. Most testers should know SQL/xml/excel and a couple of scripting languages ​​at least at a basic level.
And yes, you will most likely test not interesting games, but dull flash drives, because there are thousands of people who want to test something cool for a lot of money, plus tens of thousands of free beta testers.

Answer 2

Must disappoint you.
Low-skilled testers do the boring stuff. They pay little, demand a lot. And this is not a game for fun. A multiple check of the game in all modes, with the writing of an official detailed report. You will complete each level 100 times.
And a highly qualified tester is a full-fledged developer, with all the relevant skills. Which can easily test today, and replace the developer tomorrow. And vice versa.
Well, you won’t be able to “just play, but also pay money for it.”

Answer 3

I myself got into Game QA purely by luck - one large international mobile game development company opened a new division and recruited a large staff of testers. The requirements were only knowledge of English at a level not lower than Upper Intermediate, analytical thinking, attention to detail, ability to work in a team, basic knowledge of iOS, basic knowledge of testing theory and a love for mobile games. I also had a little experience in QA-freelance (web mostly) and experience of working in a team at one of the competitions to create a game in three days. Maybe that's why they took it.
How it works.
There is a build of the game, there is documentation for the game, there are means of communication with your testing team, and, finally, there is a bug tracker (all bugs are recorded there). There may also be various documents that need to be filled out, and there may also be tools for tinkering with remote player data on the server. At the beginning of the day, you are given the task to test a specific area of ​​the game, and it can be anything: from a specific level, to compatibility on different devices, and right up to advertising and social networks. You, taking (or sitting at) the device, open the documentation, read the parts that relate to the task, and, not forgetting to look at the team chat (and listen to what they say around you), "play" by going through the points that are indicated in task and / or documentation, checking everything clearly and not forgetting the details. If you thought you found a bug, you first look in the bug tracker, if anyone has found such a bug. If not, then you consult with your colleagues, and if everything is OK, then you file a bug in the bug tracker according to clearly defined rules and forms, not forgetting to note the number of the bug in the other documentation for the task.
It seems that everything seems to be simple, but here the tasks are very complex, incomprehensible and monotonous (and there is very little time), descriptions in the documentation are vague or absent at all, and colleagues are subject to the human factor. As a result - "what should I do, I don't understand?", headache and excitement due to the fact that a bug that you missed as too minor or not a priority according to the instructions of a higher QA will be discovered by users ... And yes, if you finished the task ahead of time - they will just give you a new one, there is always a job for testers :P Oh, yes, game QA is usually paid less than the rest of the QA...
Haven't you got tired of working as a game tester yet? Here is what, in my opinion, is needed in order to have more chances:
Something like this. Hope it helped in some way. I wish you good luck in your job search :) (Yes, start looking now!)

Answer 4

well, if the testers are completely stupid, then they just play and look for bugs, go through the same level a thousand times

Answer 5

If a programmer fixes a bug in one place, the tester checks that EVERYTHING works.