Selenium test related changes

[pkiraly]

These tests are needed to run the tests based on Docker environment work properly.

[nichtich]

Can this issue be closed? Looks like duplicate of https://github.com/pkiraly/qa-catalogue-web/issues/143

[pkiraly]

@nichtich The two tests are different. This is an integration test. It would tests a running docker instance. The other one runs the unit tests. I did not figure it out yet how to add the process to CI/CD pipeline. The ideal workflow would like this:

• if something is changed in QA catalogue the commit triggers the test
• if something is changed in QA catalogue web the commit trigger the test

The test:

1. it fetches QA catalogue
2. it fetches PICA and MARC test records
3. builds a fresh docker image
4. runs docker image with MARC related configuration
5. analyses a set of MARC records
6. runs Selenium test
7. destroy docker container
8. runs docker image with PICA related configuration
9. analyses a set of PICA records
10. runs Selenium test
11. destroy docker container
12. runs docker image with UNIMARC related configuration
13. analyses a set of UNIMARC records
14. runs Selenium test
15. destroy docker container

1-11. are implemented in https://github.com/pkiraly/qa-catalogue-uitest, but it is not triggered automatically, and is not part of a Github Action.