Using continuous integration and existing testing framework

[Xrayez]

I've made a proof-of-concept repository which utilizes Travis CI power combined with dedicated GUT command line testing ability.

There are some passing tests merged to master, and what it currently does is running cron jobs (every 24 hours), so that things like regressions can be spotted relatively easily at the moment.

Moreover, making a pull request for adding a test allows to make reproduction projects more verifiable publicly, and passing tests can be merged once fixed upstream. For instance, see current issue at Godot for which the test fail: godotengine/godot#30572. Once fixed on Godot's master, the next scheduled build should hopefully pass, see current log (with a stack trace!)

So perhaps this could be one of the ways tests can be maintained and run. WDYT?

[Xrayez]

This is now outdated with the new doctest framework in place. See topic:tests for an overview of what kind of work has been done to make it work. Thanks for discussion! 🙃