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
We need a standardized Skosmos setup for running the Cypress tests. Currently this is a bit ad-hoc and every developer has their own Skosmos installations, which may have different configurations and vocabularies.
In #1488 / PR #1496, we are switching to a dockerized Fuseki for running the PHPUnit tests. In practice, this PR already uses docker compose to start up not just Fuseki but also a Skosmos container, even though it is not yet. The next logical step is to use that container for running Cypress tests.
Parts of this are already implemented or being worked on:
PR Run cypress #1479 uses a similar Cypress/Skosmos/Docker setup under GitHub Actions CI
In addition to completing that work, these steps need to be done:
rename the init_fuseki.sh to something that covers Skosmos as well, e.g. init_containers.sh
adjust the Skosmos container so it uses the same configuration as for running PHPUnit tests
modify Cypress configuration so it uses the Skosmos container
adjust current Cypress tests so that they work with the test vocabularies we currently have
adjust documentation for running the tests (PHPUnit and Cypress) to correspond with the new situation
In the near future we probably need a new, larger and more diverse test vocabulary than the current very small ones, for example a cut down version of YSO, in order to make Cypress tests that test for advanced functionality. But that is outside the scope of this issue.
Who are the users that would benefit from the enhancement and how?
Mainly Skosmos developers.
What new functionalities would the enhancement make possible?
Running Cypress tests in a standardized environment. This also enables writing Cypress tests that are specific to a particular, known test vocabulary.
Why is the enhancement important?
This is a blocker for making substantial Cypress tests.
The text was updated successfully, but these errors were encountered:
Description of the enhancement
We need a standardized Skosmos setup for running the Cypress tests. Currently this is a bit ad-hoc and every developer has their own Skosmos installations, which may have different configurations and vocabularies.
In #1488 / PR #1496, we are switching to a dockerized Fuseki for running the PHPUnit tests. In practice, this PR already uses
docker compose
to start up not just Fuseki but also a Skosmos container, even though it is not yet. The next logical step is to use that container for running Cypress tests.Parts of this are already implemented or being worked on:
In addition to completing that work, these steps need to be done:
init_fuseki.sh
to something that covers Skosmos as well, e.g.init_containers.sh
In the near future we probably need a new, larger and more diverse test vocabulary than the current very small ones, for example a cut down version of YSO, in order to make Cypress tests that test for advanced functionality. But that is outside the scope of this issue.
Who are the users that would benefit from the enhancement and how?
Mainly Skosmos developers.
What new functionalities would the enhancement make possible?
Running Cypress tests in a standardized environment. This also enables writing Cypress tests that are specific to a particular, known test vocabulary.
Why is the enhancement important?
This is a blocker for making substantial Cypress tests.
The text was updated successfully, but these errors were encountered: