Affects Version/s: None
Fix Version/s: None
Component/s: ~ [Archived] Collaboration
Sprint:LIMA | #15 | Mar03-Mar24, LIMA | #16 | Mar24-Apr14
See https://loop.liferay.com/home/-/loop/feed/20994964 for more details.
As airports around the world are tightening up on their policies to prevent the influx of disease by introducing aggressive sanitization initiatives, stricter quarantine measures, comprehensive coverage and extensive testing, so too are we going to be doing the same to prevent regressions from happening in CI.
With the forthcoming implementation of ci:forward, we need to be aggressively maintaining and extending ci:test:relevant. This means ALL tests in the module will be run anytime ci:test:relevant is run and will need to pass in the future workflow.
This task is meant to document all tasks the Lima team needs to do in order to get our tests and suites to a point where we are ready for ci:forward.
First, assign one of the tickets below to yourself. This will scope your analysis to one app.
We'll scope backend and poshi flaky test analysis to the last three builds in
In each of the comparisons, please analyze:
- FAILED > PASSED
- PASSED > FAILED
- PASSED > BLOCKED
- BLOCKED TO PASSED to detect flaky tests
For any tests for apps not run in ci:test:lima, analyze the following upstream master builds:
- Analyze one of the components below (organized by module)
- Add any flaky tests in the description of the appropriate subtask below and include a link to each failure
- Ignore flaky tests and link that ticket to the appropriate subtask below
Attach all test fix tickets to the appropriate subtask below. Work on them as you normally would
- File a bug ticket and link to the appropriate subtask below
After all tickets linked to subtasks below are completed, then the subtask can be closed. A closed subtask means that tests running this app are 100% green in CI.