refactor: testing suite (random order)

[germa89]

Description

Implementing random order in the testing #GoodPractice.

Additionally, several more issues and changes spawned from this, like:

• Refactoring conftest.py file
• Using cleared fixture for all the tests running MAPDL.
• Fix image cache. The glyphs were offset because of Plot changes when DEFAULTS are not rebuild. #3568

Issue linked

Close #3268

Checklist

• I have visited and read Develop PyMAPDL.
• I have tested my changes locally
• I have added necessary documentation or updated existing documentation.
• I have followed the PyMAPDL coding style guidelines.
• I have added appropriate unit tests that also ensure the minimal coverage criteria.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have marked this PR as draft if it is not ready to be reviewed yet.
• I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

[ansys-reviewer-bot]

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

@ansys-reviewer-bot review

[SMoraisAnsys]

@germa89 While passing by... Would it make sense for you to use pytest-xdist ? This way you could speed up your tests by running them in parallel. If there is a limitation such that one worker has to work on a whole file, you can also use the option --dist loadfile so that each worker is provided with a test file and handling it totally.

[germa89]

hi @SMoraisAnsys

Thank you a lot for the suggestion! This is a good idea, and believe we did try it in the pass. The main limitation is that I will have to spin several MAPDL instances which is "heavy" since the docker image is huge. I think that is why we did not implement it.

Additionally, so far, our main bottleneck is on the documentation generation where I do want to implement some parallelization technique, probably having more than one MAPDL image.

I appreciate a lot you coming around PyMAPDL repo! :)

[github-actions]

Hello! 👋

Your PR is changing the image cache. So I am attaching the new image cache in a new commit.

This commit does not re-run the CICD workflows (since no changes are made in the codebase) therefore you will see the actions showing in their status Expected — Waiting for status to be reported. Do not worry. You commit workflow is still running here 😄

You might want to rerun the test to make sure that everything is passing. You can retrigger the CICD sending an empty commit git commit -m "chore: empty comment to trigger CICD" --allow-empty.

You will see this message everytime your commit changes the image cache but you are not attaching the updated cache. 🤓

[germa89]

I knew that changing the order will increase the time... but yisus.... that's a lot. And I think it is just the respawming of the MAPDL what is taking the time.... but I do not have any probe of this.

[germa89]

@pyansys-ci-bot LGTM.

[pyansys-ci-bot]

✅ Approving this PR because germa89 said so in here 😬