test: improving tests performance

[germa89]

Description

Some changes to improve testing:

• Not checking for extra MAPDL instances unless we are on DEBUG_TESTING
• Do not recreate the glyphs on each call.

Issue linked

Close #3568

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)

[germa89]

Testing if the image cache gets changed.

[Copilot]

Pull request overview

This PR targets faster (and less intrusive) test runs and plotting initialization by reducing per-test cleanup work and avoiding repeated glyph construction, and it also relaxes the optional dependency constraint for the visualization interface.

Changes:

• In test teardown, only scan/stop “extra” MAPDL instances when DEBUG_TESTING is enabled.
• Change plotting defaults so boundary-condition glyphs are configured once (cached) instead of being recreated on every access.
• Relax the ansys-tools-visualization-interface upper bound in optional dependencies.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
tests/conftest.py	Gates expensive “extra MAPDL instance” cleanup behind DEBUG_TESTING.
src/ansys/mapdl/core/plotting/plotting_defaults.py	Switches BC glyph defaults to one-time configuration/caching.
pyproject.toml	Expands allowed versions of ansys-tools-visualization-interface for optional installs.

Comments suppressed due to low confidence (1)

src/ansys/mapdl/core/plotting/plotting_defaults.py:78

• Switching back to one-time configuration means DefaultSymbol.__call__ returns the same mutable dict/PolyData instances on every access. Downstream plotting (notably legend creation and any in-place PyVista transforms) can mutate these meshes/dicts, which matches the glyph offset/flakiness described in #3568 and can reintroduce it. Consider returning defensive copies (e.g., copy the dict and deep-copy the glyph mesh) or storing factories/immutable templates so each call gets a fresh glyph object while still avoiding recomputing parameters unnecessarily.

        if not self._configured:  # Temporal patch pending on #3568
            self._set_configuration()
            self._configured = True

        return getattr(self, name)

[Copilot]

The inline note says this is a “Temporal patch pending on #3568”, but this PR is marked to close #3568. If the issue is now resolved, this comment should be updated/removed; if it’s not resolved, the PR description/linking should be adjusted because this change reverts the prior mitigation.

[Copilot]

There’s no regression coverage around the behavior that prompted #3568 (glyphs/legend geometry drifting across calls/tests). Since this change alters caching semantics, adding a test that exercises repeated BC plotting/legend creation and asserts glyph geometry stays stable would help prevent reintroducing the flakiness.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.06%. Comparing base (b2a2ed3) to head (57aff99).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4425      +/-   ##
==========================================
- Coverage   91.16%   91.06%   -0.11%     
==========================================
  Files         196      196              
  Lines       16209    16209              
==========================================
- Hits        14777    14760      -17     
- Misses       1432     1449      +17     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.