Axe results violations save

[mohanqxf2]

• Split the method "get_new_violations" in the snapshot_util file
• Display a message saying "no existing snapshots were found, we created a new snapshot. Please check the snapshot of violations and use it" when new snapshot is created.
• New txt file to save all the new violations caught while comparing with old.
• Updated the code to save the snapshot_json file under ./conf/snapshot as previously it was saving under ./utils/snapshot
• Moved the save and load snapshot json file funtions from test script to snapshot_utils.py file

To run the pytest from root dir:
python -m pytest tests/test_accessibility.py

expected Output when running first time:
| PASS: No existing snapshot was found for page. A new snapshot has been created. Please review the snapshot for violations before running the test again.

[avinash010]

@mohanqxf2

1. I don't think the failed violations are getting saved in the log file. Can you double check it?
2. Would we be updating the same violation file everytime?
3. I remember discussing, we wanted few lines of violations printed in log and the whole violations in the text file. Currently I just see a message

+------------------------------------------------+
| Tests Failed                                   |
+------------------------------------------------+
| test_accessibility:                            |
| ✗ Accessibility checks for contact page failed |
|                                                |
+------------------------------------------------+

How would the user know what's the error and where he can look for the violation?

May not be required for this PR, we need to figure out an easy way for user to accept the violation and add it to a snapshot in case they are ok with the new violation

[avinash010]

Also i feel lot of complexity is in the test.
The initialize snapshot can be a separate method and moved to utility
Violation comparison can also move to the utility

[mohanqxf2]

1. I don't think the failed violations are getting saved in the log file. Can you double check it?

@avinash010 looking at your output below, it looks like no new violations found to save in the log file

2. Would we be updating the same violation file everytime?

Yes, as of now if the violation txt file exist in the conf then its gonna update the same file.

3. I remember discussing, we wanted few lines of violations printed in log and the whole violations in the text file. Currently I just see a message

+------------------------------------------------+
| Tests Failed                                   |
+------------------------------------------------+
| test_accessibility:                            |
| ✗ Accessibility checks for contact page failed |
|                                                |
+------------------------------------------------+

Looking at this output there are no new violations caught when compared with a snapshot file, if new violations are caught then it should print the first 50 characters from each of the violations.

How would the user know what's the error and where he can look for the violation?

Along with the violations first 50 characters it will display the conf path in the output .

Could you please retry running the tests by doing a pre-request to change the HTML element contents in the existing snapshot_output_contact_page.json file which is saved under ./conf/snapshot/snahshot_output_contact_page.json

[mohanqxf2]

The initialize snapshot can be a separate method and moved to utility
Violation comparison can also move to the utility

I have moved these methods to snapshot_utils.py @avinash010

[mohanqxf2]

@avinash010 I havent pushed the latest commit yet, I will push by tomorrow. please hold of the review process. I will post here as soon the pr is ready