[MAGNOLIA-4962] UITests should immediately fail if an expected element is not around Created: 09/Apr/13 Updated: 15/Apr/13 Resolved: 10/Apr/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | integration tests |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Sprint: | Iteration 2013-14, Iteration 2013-15 |
| Description |
|
When calling AbstractMagnoliaUITest#getElementByPath(String) we don't know whether the element is actually expected to be around or not. That's why that method cannot be strict. This makes it very hard to realize what's happened in case of failures. We should support both - failing immediately when an expected element is not around as well as continuing when an element is expected to not be around. This would dramatically speed up uitests in case of unexpectedly missing elements. |