Over the past weeks we have spent a lot of time testing. When building a complex software infrastructure, it is generally a good idea to have some tools to systematically check its functionality.
Of course every software developer knows they *should* do testing, and many software projects do to varying degrees, but early on it became very clear to us that it wasn’t even an option to try to develop such a system without it.
That is more easily said than done since, in order to build a testing suite, we needed to automate and often abstract every interaction the user would have with the system (such as setting up an SVN repository and adding text files or linked .blend files).
We are already experiencing the benefits of test-driven development, which helps us foresee and verify regular and corner cases easily, while making sure that everything we’ve developed so far keeps working. The current status of the project is…
The first version of BAM is first being tested in the studio (initially by a couple of artists) so we can get some real-life feedback.
There is still plenty to do (including answering previous blog comments), so we better get back to work!
P.S. For the geeks out there, here’s some examples of test output: