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.