Feature: Visualize Test Results

[SilenNaihin]

PR Description:

This PR introduces a new feature to visualize test results. It modifies the report generation process to create directories for each test run instead of files. It also adds a new module for generating radar charts to visualize the test results. Additionally, it includes several refactoring changes and updates to the test reporting process.

---

PR Main Files Walkthrough:

-agbenchmark/utils/utils.py: Refactored the report generation process to create directories for each test run instead of files. Updated the environment variable handling and the calculation of test paths.
-agbenchmark/reports/processing/graphs.py: New file. Contains functions for generating radar charts to visualize test results.
-agbenchmark/reports/processing/process_report.py: New file. Contains functions for processing report data and extracting category information from reports.
-agbenchmark/reports/reports.py: Updated to reflect changes in the report generation process. Added a call to generate a radar chart when ending the info report.
-agbenchmark/utils/challenge.py: Added a print statement to display the task during challenge setup.
-agbenchmark/reports/processing/types.py: New file. Defines Pydantic models for report data.
-agbenchmark/reports/ReportManager.py: Updated to reflect changes in the report generation process. Added a call to generate a radar chart when ending the info report.
-agbenchmark/reports/processing/get_files.py: New file. Contains functions for retrieving the latest files in a directory or its subdirectories.
-agbenchmark/start_benchmark.py: Updated to reflect changes in the report generation process.
-agbenchmark/utils/data_types.py: Added a map from string difficulty levels to numeric values.
-pyproject.toml: Added a dependency on matplotlib for generating radar charts.

PR Quality Checklist

• I have run the following commands against my code to ensure it passes our linters:

  black . --exclude test.py
  isort .
  mypy .
  autoflake --remove-all-unused-imports --recursive --ignore-init-module-imports --ignore-pass-after-docstring --in-place agbenchmark

[github-actions]

PR Analysis

• 🎯 Main theme: Refactoring and addition of visualization notebook
• 📌 Type of PR: Refactoring
• 🧪 Relevant tests added: No
• ✨ Focused PR: Yes, the PR is focused as it mainly deals with refactoring of the code and addition of a new visualization notebook. The title and description are clear and the changes in the PR align with the title and description.
• 🔒 Security concerns: No, the PR does not introduce any obvious security concerns. The changes are mainly refactoring and addition of a visualization notebook, which do not involve any security-critical operations.

PR Feedback

• 💡 General PR suggestions: The PR is well-structured and the changes are clearly explained. However, it would be beneficial to add tests for the new functionality introduced in the visualization notebook. Additionally, the PR could benefit from a more detailed description of the changes made in the refactoring process and how they improve the codebase.

How to use

To invoke the PR-Agent, add a comment using one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe [-c]: Modify the PR title and description based on the contents of the PR. To get the description as comment instead of modifying the PR description, include the '-c' option.
/improve: Suggest improvements to the code in the PR. These will be provided as pull request comments, ready to commit.
/ask <QUESTION>: Pose a question about the PR.

[SilenNaihin]

/improve

[SilenNaihin]

/reflect_and_review

[github-actions]

Questions to better understand the PR:

1. The code changes in agbenchmark/reports/reports.py remove the calculation of non_mock_success_%. Was this metric found to be unnecessary or is it being calculated elsewhere now?
2. In the new types.py file, several new data classes have been introduced. Could you briefly explain the purpose of each class and how they interact with each other?
3. The Visualization.ipynb notebook seems to be a new addition. Could you provide a brief overview of its purpose and main functionality?
4. The internal_info.json file has had a lot of test results removed. Is this part of the changes, or is it just for the purpose of this PR?
5. The send_to_googledrive.py file no longer retrieves the non_mock_success_% metric. Is this because it's no longer being calculated, or is there another reason for this change?

Please respond to the questions above in the following format:

/answer

1. ...
2. ...
   ...

[SilenNaihin]

/describe