test dev container

[joneugster]

We should have a github action testing the dev-container is working.

This would probably be a second "job" in this github action: GameSkeleton build.yml

[liyongsea]

So each game has their own github action to check the dev container ? Will it be too complicated to maintain ?

[joneugster]

There is a github action in each game. It is this one: https://github.com/hhu-adam/GameSkeleton/blob/main/.github/workflows/build.yml

(Arguably, this issue should be there, but I'd prefer having all issues here...)

Concretely, I think one can add a second job to this github action which does the following:

• Build (and starrt) the devcontainer
• Once it's up, somehow verify that you can open the page, which is opened under http://localhost:3000 which simply redirects to http://localhost:3000/#/g/local/game
• Maybe automatically find the first (or any) level and test it works?

It's the second two steps that I have no idea if they are feasible and how you would do that.

[joneugster]

Regarding the maintaining question, the instructions currently are simply that game devs need to copy these files from the GameSkeleton if they want the newest features:

See Updating a Game

I think this is okay as is and I don't see an alternative

[abentkamp]

There are frameworks such as selenium or puppeteer that can test the functionality of a website as a whole.