cigproduction
Xfire QA - End of Day
2007-09-12 9:54 AM PDT
Mood: Happy
Today went pretty well. Kept on top of the bugs, found some major bugs… some bugs got fixed… over all good.
Working at Xfire is generally fun, Xfire QA is not as easy as everyone expects. When you find a bug at home, and wonder: “Did no-one test this?”, just remember that for every 50,000 people logged on at any one time, there is one tester with 3 rigs.
Today went pretty well. Kept on top of the bugs, found some major bugs… some bugs got fixed… over all good.
Working at Xfire is generally fun, Xfire QA is not as easy as everyone expects. When you find a bug at home, and wonder: “Did no-one test this?”, just remember that for every 50,000 people logged on at any one time, there is one tester with 3 rigs.
Xfire QA - Yellow Lung
2007-09-12 9:53 AM PDT
Mood: Huh?
One of the QA guys decided to make his daily Popcorn run down the marketing row. Marketing claims that Popcorn lung, or yellow lung is rampant in their department. I think they’re jealous of JuBu and he’s popcorn wielding powers.
One of the QA guys decided to make his daily Popcorn run down the marketing row. Marketing claims that Popcorn lung, or yellow lung is rampant in their department. I think they’re jealous of JuBu and he’s popcorn wielding powers.
Xfire QA - More Revisions
2007-09-12 9:50 AM PDT
Mood: Sleepy
Got more revisions of the client (anywhere between 200 to 600 file changes in a cycle), keyboard and mouse inputs look good. PHEW… With 900+ games supported, there’s no way we can test input changes on every single game… so we rely quite heavily on our users to let us know if we broke something.
Got more revisions of the client (anywhere between 200 to 600 file changes in a cycle), keyboard and mouse inputs look good. PHEW… With 900+ games supported, there’s no way we can test input changes on every single game… so we rely quite heavily on our users to let us know if we broke something.
Xfire QA - Meeting… in the corridor
2007-09-12 9:49 AM PDT
Mood: Tired
Company Meeting Summary: Release coming up, events, birthdays, newly bundled game, thanks everyone.
Company meetings are actually fun, everyone gets in a room together, joke around alittle, and finds out what everyone else is doing. Being buried in QA, you often forget about Marketing and Sales and even MTV.
After the meeting a conversation got started about WoW. To be specific, if Blizzard developers prefer Alliance or Horde… based on press releases, level design, and personal feelings… boy it got heated
Company Meeting Summary: Release coming up, events, birthdays, newly bundled game, thanks everyone.
Company meetings are actually fun, everyone gets in a room together, joke around alittle, and finds out what everyone else is doing. Being buried in QA, you often forget about Marketing and Sales and even MTV.
After the meeting a conversation got started about WoW. To be specific, if Blizzard developers prefer Alliance or Horde… based on press releases, level design, and personal feelings… boy it got heated
Xfire QA - Company Meeting…
2007-09-12 9:48 AM PDT
Mood: Hurried
What the screenshot system looks like from a testing point of view.
Company Meeting… BRB
What the screenshot system looks like from a testing point of view.
Company Meeting… BRB
Xfire QA - Mo' Problems
2007-09-12 9:46 AM PDT
Mood: Better
The fix for the keyboard problems are in, looks like Empires is fixed, but there are other issues now. Well more bugs, more time. Don’t worry, things should be looking good by the time we go live… hopefully.
The fix for the keyboard problems are in, looks like Empires is fixed, but there are other issues now. Well more bugs, more time. Don’t worry, things should be looking good by the time we go live… hopefully.
Xfire QA - Phew!!
2007-09-12 9:46 AM PDT
Mood: Tired
Got back, tired, sweating and possibly sick? LOL. So out of shape! Not worth the sandwich, that’s for sure.
Time to get back to testing. Just found out a fix for the WoW infoview is going in and an emergency game update for Quake Wars. It’s exciting when infoviews get fixed, because it’s a fairly simple test. With only 4.5 testers, 3 projects and 11 engineers/dev’s/web designers, things get very busy and somethings are submitted very last minute.
Got back, tired, sweating and possibly sick? LOL. So out of shape! Not worth the sandwich, that’s for sure.
Time to get back to testing. Just found out a fix for the WoW infoview is going in and an emergency game update for Quake Wars. It’s exciting when infoviews get fixed, because it’s a fairly simple test. With only 4.5 testers, 3 projects and 11 engineers/dev’s/web designers, things get very busy and somethings are submitted very last minute.
Xfire QA - Lunch!!
2007-09-12 9:44 AM PDT
Mood: Poised
OK, Lunch time. OK… I’m over-weight, there I said it… so, I decided I’m going to walk down to a sandwich shop 2 miles away… stay tuned for my possible death.
OK, Lunch time. OK… I’m over-weight, there I said it… so, I decided I’m going to walk down to a sandwich shop 2 miles away… stay tuned for my possible death.
Xfire QA - Xfire Client Release Breakdow...
2007-09-12 9:43 AM PDT
Mood: Industrious
OK, it’s testing time. The client changes a lot each week. In the 6 months I’ve been with Xfire every aspect of the client has been touched or at least looked at. This makes testing interesting, and with only 5 people testing the client, the Xfire In-game, and the web-site, we are sometimes stretched for time and resources.
Here’s the breakdown:
Week 1:
Monday – Release the client to the masses (force update at around 3PM)
Tuesday – Look for issues that may have slipped through the cracks
Wednesday – Prepare for a Game Support update, and Web Push
Thursday – Game Support update and Web Push. And work on Test Plans.
Friday – Work on Test Plans for the Cycle, and clean up.
Week 2:
Monday and Tuesday – Test new features, and modifications in the Client
Wednesday – Prepare for a Game Support update, and Web Push, continue testing features.
Thursday – Game Support update and Web Push. And work on Test Plans, continue testing features.
Friday – Continue testing features and run a full regression on the client, to ensure that nothing is missed.
Sunday Night – Feature Freeze, no new features may be submitted after this point.
Week 3:
Monday – Test all features, all modifications and perform an abbreviated the Full Test.
Monday Night – Code Freeze, no new code after this point, only emergency fixes.
Tuesday – Kirmse heads down the corridor to nervously ask how things are looking, and asks if we think we should go Beta.
Wednesday – We go Beta after 2 or 3 Release Candidates, and finding several P1 bugs that we missed before.
Thursday – We make a few more changes as needed and go to final RC and put it in the Download Channel. It shows up in everyone’s Files tab, and some install it.
Friday – More research on Bugs, and wait for dire yells of dead clients (typically from GODjonez).
And then the week starts over. Schedules are subject to change without any notice.
OK, it’s testing time. The client changes a lot each week. In the 6 months I’ve been with Xfire every aspect of the client has been touched or at least looked at. This makes testing interesting, and with only 5 people testing the client, the Xfire In-game, and the web-site, we are sometimes stretched for time and resources.
Here’s the breakdown:
Week 1:
Monday – Release the client to the masses (force update at around 3PM)
Tuesday – Look for issues that may have slipped through the cracks
Wednesday – Prepare for a Game Support update, and Web Push
Thursday – Game Support update and Web Push. And work on Test Plans.
Friday – Work on Test Plans for the Cycle, and clean up.
Week 2:
Monday and Tuesday – Test new features, and modifications in the Client
Wednesday – Prepare for a Game Support update, and Web Push, continue testing features.
Thursday – Game Support update and Web Push. And work on Test Plans, continue testing features.
Friday – Continue testing features and run a full regression on the client, to ensure that nothing is missed.
Sunday Night – Feature Freeze, no new features may be submitted after this point.
Week 3:
Monday – Test all features, all modifications and perform an abbreviated the Full Test.
Monday Night – Code Freeze, no new code after this point, only emergency fixes.
Tuesday – Kirmse heads down the corridor to nervously ask how things are looking, and asks if we think we should go Beta.
Wednesday – We go Beta after 2 or 3 Release Candidates, and finding several P1 bugs that we missed before.
Thursday – We make a few more changes as needed and go to final RC and put it in the Download Channel. It shows up in everyone’s Files tab, and some install it.
Friday – More research on Bugs, and wait for dire yells of dead clients (typically from GODjonez).
And then the week starts over. Schedules are subject to change without any notice.
Xfire QA - The Danger Zone
2007-09-12 9:43 AM PDT
Mood: Blah
So now that we’re back from the store, and I have a ton of coke in me, it’s bathroom time. Why is this significant? Because of the bathroom from hell.
Here is the door:
Notice the post-it note… that is not a joke, it’s a real warning.
So there’s a trick to using the bathroom, you need to use all your FPS skills and some WoW skills to get what you need done, done.
1. Hold your breathe (SHIFT KEY in CoD2, as sniper)
2. Open the door (E in MOHAA)
3. Stay sharp, look for any agro Yellow Jackets (red text is a dead give away, use Fade (WoW) if they’re too close to the “zone”
4. If you’re going to be in the “danger zone” for more than 30 seconds, use Stealth (WoW), to get you through the experience.
When exiting, check for stings, smells and that you still have your shoes (yes, I lost a shoe in there once).
So now that we’re back from the store, and I have a ton of coke in me, it’s bathroom time. Why is this significant? Because of the bathroom from hell.
Here is the door:
Notice the post-it note… that is not a joke, it’s a real warning.
So there’s a trick to using the bathroom, you need to use all your FPS skills and some WoW skills to get what you need done, done.
1. Hold your breathe (SHIFT KEY in CoD2, as sniper)
2. Open the door (E in MOHAA)
3. Stay sharp, look for any agro Yellow Jackets (red text is a dead give away, use Fade (WoW) if they’re too close to the “zone”
4. If you’re going to be in the “danger zone” for more than 30 seconds, use Stealth (WoW), to get you through the experience.
When exiting, check for stings, smells and that you still have your shoes (yes, I lost a shoe in there once).
