[MGNLCE-320] Re-Implement Configuration app UI-tests Created: 14/Jun/22 Updated: 14/Jun/22 |
|
| Status: | Open |
| Project: | Community Edition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | functional-tests, re-implement-phased-out-UI-test, tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
Re-Implement Configuration app UI-tests - since they have been removed (or will be removed super soon) - in order to fully get rid of old UI-tests based on Magnolia m5-UI / Junit-4. To keep it simple - and since it is unclear whether Configuration app will remain much longer - ther eis only 1 scenario to implement. Scenario: Change property value with inline editing The scenario is in place in the class it.info.magnolia.functionaltests.ConfigurationAppFunctionalTests. |