test simple ccsp file

[ShaiahWren]

[AAP-39222]

Description

Similar to the CCSPv2 test where was checked all columns and values from a built CCSPv2 report, the work at hand builds and tests the more simple CCSP one.

Much of the logic is the same with a few key changes:

• env vars now exclude 'END_USER' data such as city, state, country, and so forth.
• report excludes the 'Usage by Organizations' sheet.
• to more easily test the column in 'Usage Reporting', we will start on line 14 to grab the column header and then traverse from the top. To start at the very top introduces too much confusion because of how many blank lines there are in the top row.
• added conftest.py file to store fixtures and static methods. Refactored as needed. This change ensures that the check for SonarCloud duplication passes. Without the shared helper functions, codebase dup is > 13%. Yikes!

Prerequisites

Enter the awx virtual env

docker exec -it tools_awx_1 /bin/sh -c " cd awx-dev/metrics-utility && . /var/lib/awx/venv/awx/bin/activate && exec /bin/sh "

Steps to Test

1. From /metrics-utility run SETUPTOOLS_USE_DISTUTILS=true pytest -s

Expected Results

Both tests should pass

Required Actions

• Requires follow-on pr once we are running in standalone mode
• Add a separate fixture dir and load them from conftest.py
• Manage wb close with context manager

Self-Review Checklist

Code Quality

• Code is properly linted and formatted.
• All tests (existing and new) pass successfully.
• Tests are added or updated as needed.
• Code includes relevant comments for complex sections.
• Changes are reviewed and approved by at least two team members.
• Documentation is updated where applicable.
  - If updates are required in the handbook, create a separate PR for the handbook repo.

Notes for Reviewers

Add any additional context or instructions for reviewers here - for example screenshots if needed.

[dhaustein]

Left a few nitpicks otherwise LGTM.

I have one suggestion for the future however. While having the fixtures in conftest.py is absolutely fine, it does not scale well when the number of fixtures increases.

A trick I picked up in EDA was to create a number of semantically distinct "plugin" files for fixtures and load them in conftest at runtime. https://github.com/ansible/eda-qa/blob/main/conftest.py#L13-L39

But this is not a blocker or even a big deal right now, but might be something to think about for the future. 🙂

[MilanPospisil]

Tested and works :-)
LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud