Submitted 7 hours ago by inclementimmigrant@lemmy.world to games@lemmy.world
I was a QA tester for a mobile game company back when feature phones had games. Some of the shit was silly like jumping against the left wall 300 times would crash the game, or rapidly putting the phone into and out of a faraday cage would crash the game.
Any time we crashed the phone things got spicy, and we had special instructions to follow if we found a way to disrupt the micro cell in the office.
I also did that (and some development) and hated that basically every phone behaved differently, even sibling models from the same manufacturer. J2ME was a nice idea but every phone had different glitches. The emulators were shit. So we had almost all models of all major brands there and had to test everything on all of them.
That’s a sickass job
For every fun thing you get to test there are a dozen miserable little things that you get spend entire days plodding through. And they pay you absolute dick to do it.
Sorry, which job are we talking about again?
At the tester level it’s interesting, but past a year or two of experience it becomes more system integration and risk focused.
Source: twenty years in the industry
Seems fun until you find yourself playing the same 2 levels of “Barbie Horse Adventures” 40 hours a week (60+ during crunch) for 8 months.
7112@lemmy.world 6 hours ago
NoForwadSlashS@piefed.social 2 hours ago
This might be the best description of a good game QA that I’ve ever read