The first Testing Fixit was special, memorable, magical—I felt so connected, and loved. The second Testing Fixit was hard, exhausting work, and left me feeling lonely and borderline regretful.
2 plus ones
Shared publicly•View activity
- Having our first fixit-style thing on Nov 8, these insights have been incredibly useful.Oct 23, 2012
- Glad to hear this stuff has been helpful. Keep me posted as to how it turns out!
In fact, what's the goal of the fixit? Any schwag or prizes? A particular theme? What group have you pulled together to run it? Any other organizational details you care to share?Oct 23, 2012
- are you a Googler?Oct 23, 2012
- : No, just a fan.
: The goal is to improve our automated test documentation/infrastructure/discoverability, and get more people involved. We've never had any real engineering time behind it- it's mostly been the work of myself and a QA engineer, and as the rest of the studio adopts automated testing, there are big holes that need to be filled.
There are no prizes- I imagine the volunteers won't be that many so it feels unnecessarily indulgent. I've done similar things and prizes haven't had much impact if the contributors aren't already excited, and unfortunately we need a few more months before our engineers at large get more involved in engineering-pour-l'engineering. This largely has to do with being a game studio, not a software development company, so our interests and priorities have historically been 'anything that isn't the game isn't important.' That's been changing, though.
As for the group we have, it's myself and the same QA Engineer (we have far fewer logistical problems though, since we only have 50 or so programmers who could contribute at all). We have "Communities of Practice" though, and this fixit focuses on the Automated Testing one- so that'd be the core group of participation.Oct 24, 2012