[MGNLEE-501] Proper EE UI-test cleanup Created: 07/Aug/17 Updated: 12/Jan/18 Resolved: 12/Jan/18 |
|
| Status: | Closed |
| Project: | Magnolia DX Core |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Michael Mühlebach | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Epic Link: | Improve QA setup | ||||||||||||||||
| Story Points: | 21 | ||||||||||||||||
| Description |
|
After the CE UI-tests have been cleaned-up we should do the same for the EE UI-tests. Part of that cleanup effort should be at least:
General Tip: Write and optimize the tests in a way so that they are not EE specific. Meaning they should not rely on the Abstract EE UI Test class, they should not have EE only helper classes, etc |