-
Notifications
You must be signed in to change notification settings - Fork 48
WhatsNew
Besides technical improvements within this version we've updated the W3C validator to the most recent version (15.6.29).
This version provides mostly strictly technical changes that improve logging and release process automation.
Consider having more than one AET environment and one of them is returning errors on your page. Now it is possible to compare all patterns collected on different environment to check whether the page is really broken or maybe it is just a broken pattern. It is easier to maintain, because all environments may use the same suite, only patterns may be different.
We've added the possibility to use regular expressions in filters. Thanks to that developer is now able to filter all the messages using the same message pattern. It is useful i.e. in filtering W3C errors which may be parametrized and because of that they may differ in a small details. Regular expressions helps to handle such cases.
AET 2.0 brings new reporting capabilities and improved performance. We have decided to label the new features as BETA and improve them based your feedback as it means a lot to us. Stay tuned!
We keep evolving the AET architecture and optimizing reporting performance. We have introduced new web application reports, which are now generated on the client-side. Also, we have optimized database model queries and decreased number of calls by a factor of 10. If you’ve ever been working on a release and discovered that the AET database has become overloaded, we have removed data storage duplications so you don’t need to worry any longer!
The reporting interface has been turned into a modern and responsive client-side application. Now it’s easy to search and filter results from your test case. If you are tired of re-running your tests after accepting patterns don’t worry, now all changes are applied on the fly. Additionally you can share a link to a test result that you are concerned about and share with your team just by copying the test URL and pasting to JIRA.
AET 2.0 introduces an accessibility report that displays validation output of page accessibility analysis using the HTML_CodeSniffer library. Results show the total count of errors, warnings and notice type violations.
Now it’s possible to test client-side performance in an agile and incremental fashion. Brand new reports show overall scores along with a list of rules with individual grades. The performance analysis is based on the YSlow tool.
-
How To Use
-
Releases