As you may have seen or heard, I attended UDS-Q last week in Oakland, California. I was privileged to serve as the track lead for the QA track. I trust I served all of you brave souls willing to attend the QA track sessions well enough ;-) A big thank you to everyone who participated. We set some big goals for this next cycle, which I'd like to share over the coming days. For now, I'm going to provide the list (perhaps not comprehensive, but I tried) of blueprints I have work items on as a sneak peak at what we discussed:
You can see more of the 'qa' blueprints here:
A few key takeaways can be found in them:
- Expansion of the isotracker capabilities to do testcase management
- Ideas around helping reduce burnout, duplication of work, and in general make the testing experience easier and more fun
- Utilizing ubuntu friendly for testing
- Scrapping of the team organization ideas I proposed earlier in the cycle; instead focusing on communicating between groups will be pursued
- Ideas for community involvement in automated and regression testing
One thing you won't find in the blueprints, but which is still an important goal, is QA representation at the next UDS. I want to see more of you there next time!
So, this post was intended to be about the highs and lows of UDS. Well, let's call the first night dinner and jetlag a definite low, and the closing party a definite high :-) After 5 days of discussing I was ready to head home, but the closing party (despite the soberness of leaving) lifted my spirits and helped UDS end on a positive note.
Hmm, perhaps an image or two would better explain it..
This was high, and below is the low :-)
Latest Official Posts
