So, in order to see if everything even starts without an exception we could have a test harness where we'd launch the test, wait for 10-30s and then send an "escape" to the window.
If the launched application returns an exitCode of 0, everything is well. If a timeout happens or an exception is thrown (we might need to remove the AWT Exception Window there), the CI test fails.
Problem is: We need HW Accelerated Test Slaves. Still having such tests is good, because in the worst case, we can manually test these things after changes like a lwjgl version update etc.
This can be extended to support clever testing (checking pixels in certain render output, provided we control tpf for determinism, like for PBR to see if the color has changed due to a change in env probes or whatever).
So, in order to see if everything even starts without an exception we could have a test harness where we'd launch the test, wait for 10-30s and then send an "escape" to the window. If the launched application returns an exitCode of 0, everything is well. If a timeout happens or an exception is thrown (we might need to remove the AWT Exception Window there), the CI test fails.
Problem is: We need HW Accelerated Test Slaves. Still having such tests is good, because in the worst case, we can manually test these things after changes like a lwjgl version update etc.
This can be extended to support clever testing (checking pixels in certain render output, provided we control tpf for determinism, like for PBR to see if the color has changed due to a change in env probes or whatever).