[BUILD-1006] Look into current E2E tests and see whether they can be categorized Created: 06/Feb/23 Updated: 06/Feb/23 |
|
| Status: | Open |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Harshini Pola |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Team: |
| Description |
|
One idea that emerged out of recent #testing-qa meetings is that we want to split the current suite into multiple layers and only test the 'happy path' in the final stage. That way, the suite is slimmer and less likely to become the bottleneck it has become recently. It would be nice to take a look at the current tests and see if they can be split into at least two categories. The first would be the ones that we want to keep for sure. The others are where we are not so sure whether they really make sense at the E2E stage, and for which we want to start to find alternative implementations (with mocks in Docker containers for instance). Having this data would be helpful as base material for future discussions. |