VisualAssertions

##VisualAssertions During UI Testing there is so much aspects that may indicate that page is not working correctly (according to specification). Some of them may affect test execution (because they are laying on the test scenario path) and some of them may go by unoticed (for example brokem css rules). It's very hard to write complete set of assertion that cover full site. To simplify assertions and cover page in more detailed way VisualAssertion use screenshots to detect page changes. How does it work? During first test execution VisualAssertion takes screenshot which is marked as pattern. In the nexts test runs VisualAssertion takes screenshots and compare them with pattern screenshots. When there are changes assertion is marked as failed. When page changes intentionaly you can set error screenshot as a new pattern. You can also ignore parts of screenshot during comparision using Blind regions. VisualAssertions has a dedicated dashboard to manage screenshot patterns and browse test results. To get more infor about managing patterns check VisualAssertions Dashboard section.