-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run app tests against latest released version #611
Comments
Yes this definitely makes sense to be doing ( was something on my agenda for a long time ). For this however we need to sort out how our testing harness ( that currently lives in With running the smoke-test suites on our docker containers ( which are built periodically after a release to keep the underlying linux binaries up-to-date ) we've encountered issues, where tests have changed/improved ( or new test cases have been added due to a new feature ) and suddenly where failing the container builds. currently we solve this by tagging scenarios with Something to be later defined is the part about how often these tests should run ( every PR, every night? ) Another thought:
|
I updated the list to mention all apps that have acceptance tests. |
apps that run all core tests, like user_ldap and encryption should only run the app-specific tests with the latest release tarball |
core 10.2.1 has been released. New PRs for this issue can test against 10.2.1 |
@phil-davis Since there are no acceptance tests in Edit: But It will take ages to run. |
The same really applies to I will raise a separate issue because for that we need to discuss how and when to run all that - #625 |
Closing this as all the apps been adjusted. |
Currently we only run app tests against stable10 to make sure they will be compatible with the future OC core platform release.
This however doesn't guarantee that the current app's core runs correctly against the last released core version.
Now I'm not sure whether we want to explode the matrix of all apps to also add the last released version.
What we could do is do so only on release branches: so whenever we plan a release (RC), we'd have tests there that don't only run against core stable10 but also against the last released version (presently 10.1.0).
Not sure how to specify said version in Drone, should we hard-code ? Or fetch it from a URL ?
@phil-davis @individual-it
cc @patrickjahns for potential additional ideas
The text was updated successfully, but these errors were encountered: