28 February 2012

A Taste of QA

While cleaning up the house (King of Dragon Pass was created in our home office), I ran across a notebook kept by Rob Heinsoo, our QA lead. Here’s a typical page:

While for the most part we avoided the branching problem, King of Dragon Pass still had a lot of content, and we wanted to make sure each response of each scene was tested. Most of these had success and failure results, so our QA team had to keep track of when these happened. (It was possible to force things to happen, but I think our preference was to have them come up naturally, since in many cases things depend on something that happened earlier. Forcing a scene or outcome might be buggy in its own right.) Note that a scene might behave differently depending on clan status, e.g. R288 depends on morale.

The new scenes in 2.0 went through a similar process to make sure every branch and outcome worked.

1 comment:

  1. Looking at that I'm once again glad I only had to do the fun parts.