Introducing the QA team!
Sep. 12th, 2005 03:37 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
shirenomadThough it was about time to describe where I work. Allen runs the department, Hacker's one of the subordinates, and the others are Fei and Thomas. Michael's a summer intern who'll only be around for another week. (And Brian, the guy I've been rooming with, is the System Administrator for the office. For those not familiar with that term, that means he keeps all the computers in the office running smoothly.) For now, I'm sharing Thomas's cubicle, and Michael's sharing Hacker's; when we move to the larger office around the end of the month, we'll get a bit more room. We'll also bring on a few more QA staffers at that point.
I can't talk about the software too much -- confidentiality agreement -- so I'll just call it "the software" here and in the future. But just know that the job of the QA department is to make sure it works. Or rather, make sure it DOESN'T work. Our motto: it's not a good day until we've found at least five things to complain to the programmers about. ^^ Over the five days I've worked so far, I've found three "criticals" (which means crashes, loss of data, and/or blatant error messages), and a whole mess of smaller glitches. Those get logged, the programming department attempts to fix everything, and then when they think they have, they pass the new version to us and the whole checklist gets run through again. It's a living.
I can't talk about the software too much -- confidentiality agreement -- so I'll just call it "the software" here and in the future. But just know that the job of the QA department is to make sure it works. Or rather, make sure it DOESN'T work. Our motto: it's not a good day until we've found at least five things to complain to the programmers about. ^^ Over the five days I've worked so far, I've found three "criticals" (which means crashes, loss of data, and/or blatant error messages), and a whole mess of smaller glitches. Those get logged, the programming department attempts to fix everything, and then when they think they have, they pass the new version to us and the whole checklist gets run through again. It's a living.
