REFACTOR: 12_post_processing refactoring

[nunesanderson]

Description

Post processing test refactor

Issue linked

Please mention the issue number or describe the problem this pull request addresses.

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate tests (unit, integration, system).
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved by the PR if any.
• I have agreed with the Contributor License Agreement (CLA).

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.49%. Comparing base (d48283a) to head (a4b176f).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6051      +/-   ##
==========================================
- Coverage   85.15%   82.49%   -2.67%     
==========================================
  Files         167      167              
  Lines       63153    63157       +4     
==========================================
- Hits        53781    52101    -1680     
- Misses       9372    11056    +1684     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gmalinve]

@nunesanderson thanks for taking care of this! :)
Here some suggestions:

• I'd improve the test method names (test_manipulate_report_A, B, C etc.)
• All tests don't have a single purpose, they assert multiple methods.
• There are some methods that are asserted more than once in different tests (just as an example you can look at export_config and create_report_from_configuration just to mention a couple). We could check if there are repetitions without decreasing codecov.
• There are also some tests (test_parse_vector) where we test protected methods (is it really needed?). We can check.
• There are some tests, just as an example test_markers that creates multiple field plots to test markers. Maybe we could avoid some cases and open an aedtz where the field plot is already created.

[gmalinve]

@nunesanderson remove.