Run Cypress tests for demo apps in CI

[DrRataplan]

These break too often, indicating they are not always executed before every commit. I hacked together a github CI flow that:

• Installs current Jinks in a new container
• Generates the demo apps
• For each app:
  • Download it using XST
  • NPM installs it
  • Runs npm run test on it

Sure, reporting could be prettier. But we need automated tests.

Some notes:

Tests fail (to no surprise). But most of them succeed.
Some fail hard: the ones in browse.cy.js make Cypress error out with a SIGSERV. They need attention. I had to disable them for now.

[duncdrum]

Lots of good stuff. Thanks @DrRataplan

However I would

• reuse the test image from the container setup, when running app tests.
• Execture TP, Serafin, and Workbench in parallel instead of sequentially for better and more targeted feedback. Right now if Serafin fails, workbench never executes.
• the SIGSEGV error is a regression and should be fixed and reproduced in the components repo.
• Tests need to use -b firefox as it prevents the electron crash

[duncdrum]

needs a bit more work:

• the test exclusions need to go, these test pass (outside of electron)
• we need to streamline the container generation and reuse,
• make sure all actions scripts are on latest version.

I ll add to the PR later

[duncdrum]

ok I m going to rebase to bring the latest hotness from main

[duncdrum]

here goes: Test are running, no SIGSEGV the failures in tp-workbench and serafin are real.

jink-demo images (which are used during tei-publisher releases) are only deployed to the registry after all tests pass. So no test fixes no new image for a tei-publisher release

streamline the whole operation. We were generating apps and passing them around before, this makes more use of that, and the container we already build with these apps.

lots of refactoring to hopefully ensure things run smoothly during jinks releases

its fixed

[duncdrum]

@DrRataplan can't request you as a reviewer but have a look if this does what you want.

[duncdrum]

• 1 Failing test on tp-workbench looks like something we fixed for tp-app recently, the fix apparently needs to be ported to another profile.
• two skipped specs in tp-serafin related to sidebar and navigation, did someone change stuff without adjusting tests?

[duncdrum]

but what about a roaster update??