|
User need
From: https://folio-project.slack.com/archives/GNZPCM00J/p1573221932054700?thread_ts=1573144008.050000&cid=GNZPCM00J
... run our full nightmare integration tests in an automated fashion. those are nice bc they implicitly test both the frontend and backend at the same.
they need to run against a live backend, so the obvious example is the nightly integration tests that are run for the core modules (eg https://jenkins-aws.indexdata.com/job/Automation/job/folio-snapshot-core/230/UI_20Regression_20Test_20Report/)
i don’t (and i assume everyone else agrees) want to run our tests to run as part of that suite, but perhaps separately somehow…? leveraging the infrastructure that’s in place for those?
Summary
- run a series of stripes-testing/nightmare integration tests (defined in ui-agreements and ui-licenses currently) nightly
- (and ideally, in the future be able to run them as part of github PRs)
- see the output of them somehow (slack channel, etc)
- not have their output trigger or prevent the triggering of anything. (ie, a failed run of core integration tests prevents promotion of folio-snapshot-stable)
- in a perfect world, be able to manually trigger runs
|