Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated tests #19

Open
curiousdannii opened this issue Jun 12, 2016 · 2 comments
Open

Automated tests #19

curiousdannii opened this issue Jun 12, 2016 · 2 comments

Comments

@curiousdannii
Copy link
Member

For Kerkerkruip we run some automated tests on Travis: https://travis-ci.org/i7/kerkerkruip/builds/53228540

Is this something that could be useful to set up for CM? What kind of regressions would we like to check against? Just using the built in tests?

@angstsmurf
Copy link
Contributor

angstsmurf commented Jun 12, 2016

Simply running TEST ME, TEST ME2 and TEST HARD and then reporting any differences in the transcript would be a great start.

Of course it would be amazing to have a way to tell if a code change improves performance or slows it down. Would the time taken to run the full-game tests be a useful measure of this?

@curiousdannii
Copy link
Member Author

Of course it would be amazing to have a way to tell if a code change improves performance or slows it down. Would the time taken to run the full-game tests be a useful measure of this?

Yeah that would make sense - it would be a lot better than micro benchmarks too. Travis works for pull requests, so if there's a controversial change and we had it doing a profile run as a matter of course, then that would make it really easy to see the effect of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants