[MAGNOLIA-4350] Page editor integration tests should not rely on samples Created: 27/Mar/12 Updated: 04/Apr/16 Resolved: 04/Apr/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | integration tests |
| Affects Version/s: | 4.5.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
"ftl-sample-site" page from samples project is currently used to lookup DOM elements and make assertions about page editor behavior. Obviously we need something more stable as css and page structure might change in samples and increase chance of failures. |
| Comments |
| Comment by Michael Mühlebach [ 04/Apr/16 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |