There's two major "types" of game testing/QA. Publisher and developer.
Publisher QA is like AttackingHobo's comment, where you're mostly sitting in front of a game in a cubicle with tons of other people around you, and you're turning the game on and off to make sure it doesn't crash. Or you're running into every single wall to make sure there's no seams in the geometry. And you're doing this for 12 hours straight, and getting paid $8/hour, and you better show up early tomorrow if you want to keep the job. This is the game industry equivalent of a retail position. Low pay, long hours, not much chance for advancement unless you're promoted to manager of the team. It's often a temp job where you might not work for 3 months because there's no games to test.
Developer QA is more in line with the automated software tester position you have now. You work with the team who is developing the game, pointing out major bugs, being able to provide useful feedback that could impact the game, and possibly deal with build issues, or other things. Developer QA is generally full time, salaried, and will be hired by studios like all the other jobs. You're probably not going to find too many QA positions at small indie studios, but a "larger" studio might have openings.
This is just a broad overview, and as always, there's going to be differences depending on your location and other things. Josh's answer covers salary and job prospects fairly well. Realise that the game industry is competitive, and less stable than a typical software job.