It was suggested on today's status call to create some basic and automated testing scripts to help validate that we've reached feature parity with Ergast and to ensure that while we are fixing items during beta testing that we don't inadvertently introduce regressions.
I think this can be closed as we already have tests comparing against ergast responses for parity and preventing regression.
See here: tests/fixtures/ergast_responses
It was suggested on today's status call to create some basic and automated testing scripts to help validate that we've reached feature parity with Ergast and to ensure that while we are fixing items during beta testing that we don't inadvertently introduce regressions.