AET Accessibility Issues Provider

[radeklawgmin]

From to time there are suites that contain a lot of urls and generate a lot of accessibility issues. The problem is when there are a lot of issues that breaks the same rule. Going from url to url and collect them manually can be a real pain.
To make this more efficient we will need:

• a feature that will collect such issues in a form of formatted data,
• issues should be collected in a dedicated report in txt and xls formatted files,
• the format should allow to paste errors into JIRA tasks,
• the format should allow to filter errors according to their type.

Tech notes:

• implement/migrate the report generator into the core, align all interactions with DB with the project's way of doing things
• add appropriate OSGi service for requesting report generation
• service should be provided with information as to what report to generate (based on correlation ID, report type, report verbosity level...)
• add REST endpoint for generating and downloading the report
• add REST endpoint for querying for report availability on given suite (checking if the suite has accessibility at all)

[annabudziszewska]

Issues founded for version 3.3.1.SNAPSHOT

1. Documentation should be adjusted:
   documentation/src/main/wiki/AccessibilityIssuesReport.md
   In section 'Downloading the report' in URL, 'type' should be replaced by 'verbosity'

2. Documentation is incoherent with the implementation
   In report URL, WARNING is not working (as described in documentation), but 'WARN'
   So this is working URL: http://localhost/api/accessibility/report?company=cognifide&project=pro&suite=sui&correlationId=corrID&verbosity=WARN&extension=txt
   So this is NOT working URL: http://localhost/api/accessibility/report?company=cognifide&project=pro&suite=sui&correlationId=corrID&verbosity=WARNING&extension=txt

3. XLSX file generated with NOTICE verbosity (0 issues) , cannot be opened. The following error occurred

4. Report should have an information with issue level (NOTICE, WARNING, ERROR)

[annabudziszewska]

Above issues have been reported in separate tickets:
#591
#592
#593
#594