vastra-gotalandsregionen/verifierad-deprecated

Projekt för att kontinuerligt övervaka en webbplats mätbara kvalitetsfaktorer.

verifierad-deprecated's Issues

contentCheck and mobileFriendlyCheck don't log all entries

mobileFriendlyCheck seem to not like new request at a high pace, and contentCheck writes URL in the terminal that has no trace in the report.

The documentation is really outdated...

Should we focus on a stable release for now, or update the documentation?

Test automation

Write tests for 100% coverage and automate testing using Travis.

Use Lighthouse

Perhaps Lighthouse would be a great complement, for technically/development inclined:
https://developers.google.com/web/tools/lighthouse/

Google's API for mobile friendliness not reliable

Still a couple of months since launched as a beta API it often fails when testing URL's continuously. Each URL taking about 30-40 seconds to get a response makes it a not that reliable option for large websites.

Is there any other options out there? Should we post-pone the support for this API?

Write report every n checks

Refactor the report writing to support continuously writing reports, for instance every 5000 checks against an API.

Create a more noob-friendly report (also for those busy ppl)

As I found out (thanx Linda K for pointing it out), not everyone loves the data-driven approach of our reports we've been offering thus far.

Suggestion

Figuring we should write two reports. One is the CSV for the data-driven-decision geeks, but also a HTML-report focusing on:

1. worst offenders on each especially important criteria.
2. statistics to be referred to on a later occasion
3. statistics where applicable and comparable to given threshold values, such as Flesch-Kincaid for readability

This supports a more action-driven insight going forward.

Checks: Refactor out to own files

Refactor out all checks to their own logical files based on provider.

Plus:

• PEP8 the code
• Simplify and refactor out functionality for reusability by other checks