Radek Lawgmin
Radek Lawgmin
Thanks for raising it. Yes, the idea looks interesting and is worth considering, although it may be hard to introduce it pretty soon as it will change the way AET...
Yeah, the idea is that AET is not a cross-browser testing tool nor the tool to compare a site among different browsers, however one may need to track changes in...
It should like the issue raised by Kube extends #535, so they can be addressed together
What about the case when: - the user spots a difference (e.g. some layout change on the mobile viewport) that she/he does want to be bothered with, so she/he makes...
It looks like the issue still exists (AET 3.2.2).
Thanks for this improvement. I agree that it is a very useful feature once there are some issues with tests and no doubt it can help much to solve potential...
Hi @wojdaa, Thanks for raising this. Could you describe how this feature should work like? Would you like AET to run tests cases against the urls you will need to...
Hi @mgifford, Thanks for raising this idea. It looks really interesting. We will take a look at it. By the way, remember that you can always contribute to the project....
It would be great if we could integrate AET with Lighthouse SEO audit that can be run: - in Chrome DevTools, - from the command line, - as a Node...
Note that a similar issues has been raised for the performance audit - perhaps these two can be done together. For details see #368.