馃殌 Feature Request
When locator assertion fails, I get now dump of whole page in aria snapshot:
expect(self.get_locator(xpath)).to_be_visible()
E AssertionError: Locator expected to be visible
E Actual value: - complementary "Sidenav":
E - list:
E - listitem:
E - img
E - img
E - listitem:
E - img
E - text: Final touch
(...)
It pollutes logs, and requieres custom wrapper around assertions. Also since I always look in videos / screenshots to understand failure, so looking into DOM structure is a last resort. I didn't find an option to disable it.
IMHO such heavy logging on assertion is overkill, and should have option to at least disable it. Even better option - enable only when tracing is explicitly enabled.
Example
No response
Motivation
Logs are polluted and hard to read, by dumping whole page structure on failed assertion.
馃殌 Feature Request
When locator assertion fails, I get now dump of whole page in aria snapshot:
It pollutes logs, and requieres custom wrapper around assertions. Also since I always look in videos / screenshots to understand failure, so looking into DOM structure is a last resort. I didn't find an option to disable it.
IMHO such heavy logging on assertion is overkill, and should have option to at least disable it. Even better option - enable only when tracing is explicitly enabled.
Example
No response
Motivation
Logs are polluted and hard to read, by dumping whole page structure on failed assertion.