wait i'm confused. i vaguely understand what you do with game testing, but how do you actually test random WORD PROCESSORS or like printers (i am assuming this is the type of hardware you mean). do you just run it through a set cycle of tasks repeatedly?
ugh. i'd hate having to test something boring like printers. but i guess the possibility would always be there for doing that.
anyway, you're right in thinking that you just perform a series of tasks repeatedly. when it comes to testing something multi-functional like a piece of hardware, checklists ultimately need to be created that the tester can use to effectively run a manual diagnostic of the performance of the device relative to its intention by the developer. in my case, i've been working exclusively on video cards and their relative device drivers(for a company everyone has heard of). video cards are naturally very complicated as far as this process goes because they have a very broad range of literal functions, so the checklists we get really need to consist of test cases that represent a wide variety of tasks any user of the device may do. so much of this is just dicking around with computer interfaces and running every damn type of media that the videocard is designed to interact with. when you get to this point, it's really just a matter of making sure the thing operates as advertised, so you leave a lot of it up to the eyes of the tester.
from there, this becomes more complicated when you consider that we need to test cards and drivers with systems that are theoretically supposed to represent a wide variety of systems currently on the market. you really need to have a couple dozen testers on projects like this, as the various checklists get completed hundreds and hundreds of times. then you get checklists and general assignments where the client wants to see if the device will operate under some absurd fucking condition that will break the system(this is when everything becomes hilarious).
although i'm probably misspeaking a bit here, because every test cycle is different to some extent, so i'm really only referring to my experiences. but still, the developers know what the object to be tested was designed to do. as testers, you have to make sure that their
assumptions are correct, or document it when they're incorrect. it looks like a really complicated process on the outside, but it really isn't once you get into it. you just sit down with the object(be it a game or a printer) and literally do all the things it's supposed to do.
also i am probably a little lucky because i am ACE TESTER HUNDLEY and i get to do all the wacky, bonkers shit we get in from the client. this is neat because the job is not repetitive at all, but the downside is that i don't get to just sit back and fuck around in bioshock for half an hour waiting for something in the game to ruin the day of some dwarf software engineer in india.