Nightly Development Builds #33
Comments
|
JupyterHub does something similar to what you suggested I think, but in the same project. It has a dependency on They test JupyterHub against the PYPI version of They use an environment variable, to have an extra job that validates the master branch. We could have something like this in Cylc Flow for isodatetime (maybe allowed_failures=True), and also for cylc-uiserver for cylc, and cylc-doc, sphinx-extensions, etc. Just in case it gets too hard to have a separate project in cylc-admin for running these tests 👍 (I don't have a preference, just thought worth mentioning what I found in JHub) |
|
Idea for end-to-end testing:
Good for testing mutations, interactions, etc. Would probably require one workflow per test, may be able to perform the setup/teardown within the Cypress test spec. |
* Partially addresses cylc#33 * Add a nightly build which installs the Cylc components for each supported Python version. This will help to detect metadata, dependency and branch conflict issues. * Future work can add end-to-end tests which engage all of the system components.
* Partially addresses cylc#33 * Add a nightly build which installs the Cylc components for each supported Python version. This will help to detect metadata, dependency and branch conflict issues. * Future work can add end-to-end tests which engage all of the system components.
* Partially addresses cylc#33 * Add a nightly build which installs the Cylc components for each supported Python version. This will help to detect metadata, dependency and branch conflict issues. * Future work can add end-to-end tests which engage all of the system components.
* Partially addresses cylc#33 * Add a nightly build which installs the Cylc components for each supported Python version. This will help to detect metadata, dependency and branch conflict issues. * Future work can add end-to-end tests which engage all of the system components.
* Partially addresses cylc#33 * Add a nightly build which installs the Cylc components for each supported Python version. This will help to detect metadata, dependency and branch conflict issues. * Future work can add end-to-end tests which engage all of the system components.
[as discussed at Exeter meetup June 2019]
Now that we have separated Cylc components into multiple repositories we need to do periodic (e.g. nightly) builds to ensure compatibility is maintained.
This should be done on an umbrella repository (i.e. this one), the test battery could compose of a limited subset of tests from each component along with some purpose written integration tests.
The text was updated successfully, but these errors were encountered: