ci: using strict markers on pytest

[germa89]

Description

To catch warnings

Issue linked

NA

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)

Summary by Sourcery

Enforce strict pytest markers and update test marking conventions throughout the suite

CI:

• Enable strict marker enforcement in pytest configuration

Tests:

• Rename the 'gui' marker to 'requires_gui' and add a new 'console' marker
• Replace deprecated pytest.mark.fail with pytest.mark.xfail in test_launcher
• Switch @pytest.mark.trylast to @pytest.hookimpl(trylast=True) in the pytest_configure hook

[sourcery-ai]

Reviewer's Guide

Enforce strict pytest marker usage by updating configuration, standardizing marker names, migrating a deprecated hook decorator, and correcting an expected-failure marker in tests.

File-Level Changes

Change	Details	Files
Enforce strict markers in pytest configuration	Added '--strict-markers' flag to pytest addopts Renamed 'gui' marker to 'requires_gui' Added new 'console' marker	pyproject.toml
Migrate deprecated pytest decorator to hook implementation	Replaced @pytest.mark.trylast with @pytest.hookimpl(trylast=True)	tests/conftest.py
Correct expected-failure marker in test	Changed pytest.mark.fail to pytest.mark.xfail in test_launcher	tests/test_launcher.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[ansys-reviewer-bot]

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

@ansys-reviewer-bot review

[sourcery-ai]

Hey @germa89 - I've reviewed your changes - here's some feedback:

• Under --strict-markers, you’ll need to declare xfail (and any other custom markers you’re using) in the markers list, otherwise pytest will error on unknown markers.
• The new console marker name may be ambiguous—consider renaming it to something like requires_console for consistency with requires_gui.
• Switching to @pytest.hookimpl(trylast=True) relies on a newer pytest API—double-check your minimum pytest version in CI to avoid compatibility issues.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.27%. Comparing base (55914e8) to head (e47d352).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3934      +/-   ##
==========================================
- Coverage   88.29%   88.27%   -0.03%     
==========================================
  Files         187      187              
  Lines       14830    14830              
==========================================
- Hits        13094    13091       -3     
- Misses       1736     1739       +3     

🚀 New features to boost your workflow:

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

[germa89]

@pyansys-ci-bot LGTM

[pyansys-ci-bot]

✅ Approving this PR because germa89 said so in here 😬