[MGNLTEST-133] Run self tests against multiple magnolia versions Created: 17/Dec/20 Updated: 16/Nov/23 |
|
| Status: | Open |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Rishab Dhar | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | TAE | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Date of First Response: | |||||
| Epic Link: | TAE-build-or-infra-tasks | ||||
| Team: | |||||
| Description |
|
The self tests right now run always against the latest snapshot of magnolia. Often times, self tests start failing with newer snapshots. In order to disambiguate the root cause of the failures, consider parameterizing test runs against older release and the newer snapshot on Jenkins. Implementation notesThis would be easy to do using Jenkins' matrix directive: https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/ If the pipeline was able to automatically resolve the Magnolia bundle version before the current SNAPSHOT, it could create a simple matrix and run tests on both bundles. This would apply to all jobs that use the moduleUiTestsPipeline, but that wouldn't be a problem?
|
| Comments |
| Comment by Christoph Meier [ 09/Nov/23 ] |
|
Tp precise tha a bit: Since we soon split into
The former we will run against 6.3-SNAPSHOT Once we have the above mentioned change in place - would that sufficient, rdhar ? |