mefisto94 / jme3-testing Goto Github PK

It would be nice to spin this unit tests inside an AVD to test our android support as well.
Investigate what is required, there definitely are tools to run unit tests on AVD

https://github.com/jMonkeyEngine/jmonkeyengine/actions/runs/929511145

Apparently from a quick look the lwjgl2 context doesn't even properly start, because the logging output stops after printing the jme version and keeps locking the jvm for every test.

If you look at the results from lwjgl3, there you can see multiple contexts spinning up.

Forking happens on a per-class base, so a lot of our tests run on the same JVM, where one hangup causes trouble down-the-line, also side effects can't be avoided that way.

The only real fix is moving out the current structure into loads of small classes, trying to keep everything clear enough.

Try to load an nonexistant asset in SimpleTestApplication#enqueue.
LWJGL3 will stop at sta.start() and won't catch the Exception, but the Test won't fail and the Uncaught Exception Handler isn't thrown either.