xrayez / godot-testbed

[WIP] CI automatic testing environment for Godot Engine

There exists a power set of possibilities. The following is just a subset of what is possible to do in our universe of discourse. My interests and skills just happen to have an intersection with this set. 😁

Game developer

✔ Skills

• Bachelor of Computer Science
• Engine/tools Development
• Computational Geometry
• Image Processing
• Physics (predominantly 2D)
• Music Production

🎯 Future

• Reinforcement Learning

Publications

Software Development Ethics

• Waiting for Blue Robot - How To Make an Open-Source Community-Driven Project, Manage It and To Remain a Human.

📫 Contacts:

• Discord: xrayez
• Twitter: https://twitter.com/Xrayez
• GitHub: If I don't respond, feel free to ping me: @Xrayez.

godot-testbed's Issues

Refactor issues testing to unit test suite

It makes sense to have a separate test folder for specific issues which are complex in nature (can contain scenes, materials etc). Yet so far most "crash" issues can be refactored into unit test per class.

CI: run tests in release mode

Despite what Travis CI reports as success, there's no tests which are run in release.

IIRC it's not possible to pass command line arguments to release (export) binary, but GUT has this script exporting feature:

https://github.com/bitwes/Gut/wiki/Exporting-Tests

Also see bitwes/Gut#73.