Performing QA in a web environment is much different than QA in a client/server production environment. I literally spend my whole day testing, assigning defects, and then assigning them to devs. Since I am a dev of sorts, it sure hurts my feelings to have to do it. :-)
Most of our devs are pretty cool, and we all get along great. There is *so* much to do when updating a web site like ours, no one really has time to fuss much.
The team has been teaching me our manual process so far, and I had my first day of dynamic web development/testing today. Found a few, they were fixed and retested, and found a few more...and so on. I don't mind manual testing, but I came here expecting to work on automation. I do know our automation is done via a homegrown .net project that bolts on to our existing testing software. We did this rather than use some of the Mercury tools.
I have been told by someone sitting near the manager that the head of the automation team will most likely approach me on Monday about doing some. Can hardly wait. :-)
In the interim, I've been working on the BattleshipNet game, and most recently, an alarm clock for my PDA. Who knew the stock "alarm" on it was so weak?