If you were to ask “What are the most difficult aspects of testing a game engine,” an answer you’d hear a lot is “rendering.” What things look like when they’re drawn to screen–how do you test that? Well, to know that things drawn to screen look right you need to compare the rendered image to an image you can expect to be static, unchanging. The first approach is to create an image test fixture of the expected render image and compare that against the render image itself. However, this approach is extremely limited. As unfortunate as is is, we must leave the domain of simple static tests, and enter into the wacky world of dynamically testing.
The example used for testing is a game where you eat sugary things until you lose all your enamel (effectively making enamel HP)! Lillian shows how the aforementioned is tested. The TDD part comes in when someone asks to show a Test Driven Development example where brushing your teeth restores enamel.
It’s about 20 minutes long, includes questions/comments from the crowd.
Here’s the repo being talked about in the video: https://github.com/LeadPages/tutorials
The basics of writing tests in Python, as explained by a very tired and unprepared me (Lily Lemmer!). ?
I had just come back from vacation and forgotten I was to give a talk on this subject, so I was unprepared and a bit sick as you can hear from my voice, so please be forgiving. ? I’ll be doing this talk again, it should be a lot better! Keep a lookout!