Unittesting import picard data

[Yu-jinKim]

• Restructuring of code to separate tests pertaining the MultiQC report object itself and the tests for checking the data
• Test to check the data for Picard alignment summary metrics
• use setUpModule instead of setUpClass for set up of multiqc reports and import in test database
• remove duplicated code between test_import_fastqc and test_import_picard functions

---

This change is 

[pep8speaks]

Hello @Yu-jinKim! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file trendyqc/trend_monitoring/tests/test_multiqc.py:

Line 44:1: E302 expected 2 blank lines, found 1 Line 92:80: E501 line too long (80 > 79 characters) Line 114:80: E501 line too long (89 > 79 characters) Line 136:35: W291 trailing whitespace Line 173:80: E501 line too long (82 > 79 characters) Line 300:80: E501 line too long (80 > 79 characters) Line 368:80: E501 line too long (81 > 79 characters) Line 425:80: E501 line too long (111 > 79 characters) Line 441:80: E501 line too long (82 > 79 characters) Line 494:80: E501 line too long (83 > 79 characters)

Comment last updated at 2024-04-17 09:39:45 UTC