[MGNLTEST-46] Page objects can handle M.-5-ui and M.-6-ui "elements" Created: 17/Sep/19 Updated: 07/Jul/20 Resolved: 31/Oct/19 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Federico Grilli |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | core-TF-features-bugs-improvements |
| Sprint: | now |
| Description |
|
Make sure the page objects - mainly for content apps - can handle both
(See _What are the Magnolia 6 and Magnolia 5 UI frameworks) The page objects figure out automatically whether a "selected" app / element / whatnot is of M.-5-ui or M.-6-ui type. This may concern more than the ContentApp class only; we may also have to check Form, Grid, etc.
Use cases so far: Assets-app, definitions-app
|