[FOLIO-2954] Disable Nightmare/"UI integration tests" in daily folio-snapshot reference CI builds Created: 08/Jan/21 Updated: 29/Jan/21 Resolved: 29/Jan/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps: Sprint 105, DevOps Sprint 106 |
| Development Team: | FOLIO DevOps |
| Description |
|
The nightmare tests are no longer maintained. Therefore execution of these tests in CI should be disabled for folio-snapshot reference builds. The additional CI code which tags 'folio-snapshot-stable' should be disabled as well. Once this is complete, merge Zak Burke PR to remove the test code from platform-core. https://github.com/folio-org/platform-core/pull/793 |
| Comments |
| Comment by Zak Burke [ 10/Jan/21 ] |
Certainly right now, folio-snapshot-stable is uselessly out of date and could be turned off to save the resources. Long term, though, I don't know if that's the right call as the goal is to write (and maintain!) new end-to-end tests. Anton Emelianov, Craig McNally, any thoughts on whether we should stop tagging snapshot-stable, and whether it can be temporarily or permanently shut down? |
| Comment by John Malconian [ 29/Jan/21 ] |
|
For good measure, I've disabled the code in the Jenkins folio-snapshot build pipeline that executes UI integration tests. It's only commented out so that it can be easily re-enabled if necessary. |