You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #360 which upgraded DS to use LWJGL3 on the backend. Unit tests are still somewhat new to DestSol unlike for Terasology, which has some advanced headless capabilities. During work on #360@BenjaminAmos noted as follows:
This breaks the unit tests, due the the new backend not being able to run in environments without a running X server ("X11: The DISPLAY environment variable is missing"). This could be resolved by using the headless LibGDX backend, which I have implemented on my lwjgl3-upgrade-tests-fix branch. The commit is BenjaminAmos/DestinationSol@9626f35.
I included the additional fix when merging and everything is fine as-is in Jenkins and elsewhere. However we should spend a bit of research time in this area to see if the updated approach is the way to go or if we should look at alternatives.
As such this might be more of a long term reminder to dig deeper when we get a chance to focus on automated testing for a while. Also may be worth looking what's out there in LibGDX land when it comes to testing utilities. Maybe we could even use some of those for Terasology one day!
The text was updated successfully, but these errors were encountered:
Follow-up to #360 which upgraded DS to use LWJGL3 on the backend. Unit tests are still somewhat new to DestSol unlike for Terasology, which has some advanced headless capabilities. During work on #360 @BenjaminAmos noted as follows:
I included the additional fix when merging and everything is fine as-is in Jenkins and elsewhere. However we should spend a bit of research time in this area to see if the updated approach is the way to go or if we should look at alternatives.
Consider researching the headless testing related code in Terasology to see what we could bring over, including the https://github.com/Terasology/ModuleTestingEnvironment/ which lets you script out headless tests and even the Record & Replay system detailed at https://iaronaraujo.wixsite.com/meusite/blog/google-summer-of-code-2018-final-report - just keep in mind DS likely isn't ready for either of those approaches due to insufficient architecture, particularly not having implemented the entity system yet.
As such this might be more of a long term reminder to dig deeper when we get a chance to focus on automated testing for a while. Also may be worth looking what's out there in LibGDX land when it comes to testing utilities. Maybe we could even use some of those for Terasology one day!
The text was updated successfully, but these errors were encountered: