Switch test suite to pytest and update CI workflow to support pytest

[JaskRendix]

PR updates the test suite to use pytest. The current CI workflow fails because the reusable workflow runs nose2, which cannot execute pytest tests. The suite uses pytest features such as fixtures, parametrization, and monkeypatch, so nose2 cannot run it. To restore CI compatibility, the reusable workflow needs to support pytest. Possible solutions:

1. Replace the nose2 command with pytest:

   pytest -vv --cov
   

2. Add an input to select the test runner:

   test-runner: pytest | nose2
   

   and switch based on that value.

3. Add an input that allows callers to override the test command.

The test suite passes locally under pytest and requires CI support for pytest to run correctly.

[JaskRendix]

@ppizarror quick question about the CI setup.

Right now the repo uses a reusable workflow:
uses: ppizarror/workflow-actions/.github/workflows/test_python.yml@master

Would you prefer:

• Moving the entire test logic directly into the main CI workflow, so everything lives in one file,
• Updating the reusable workflow to use pytest instead of nose2, and keeping the current structure?

Just want to align with your preferred direction before I touch anything.

[ppizarror]

Hi. I will update the workflow, adding a "test_engine": pytest

[JaskRendix]

@ppizarror ok, let me know when it's ready, eventually you could replace:

if [ "${{ inputs.coverage }}" = "true" ]; then
  nose2 --verbose --with-coverage ${{ inputs.nose-args }}
else
  nose2 --verbose ${{ inputs.nose-args }}
fi

with

if [ "${{ inputs.coverage }}" = "true" ]; then
  pytest --cov=pygame_menu
else
  pytest
fi

[ppizarror]

Hi @JaskRendix . I've added a "engine" param, so in this case, workflow should be edited with
... engine: pytest

Followed your guidelines, hope it works: ppizarror/workflow-actions@2577eb7

[JaskRendix]

@ppizarror we need to merge the other PR with the updated pyproject.toml first. Once that’s in, the workflow will pick up the new test extras and everything should work with engine: pytest as expected.

[ppizarror]

@ppizarror we need to merge the other PR with the updated pyproject.toml first. Once that’s in, the workflow will pick up the new test extras and everything should work with engine: pytest as expected.

merged. Lets see how that works.

[JaskRendix]

@ppizarror now everything runs. I bumped into failing tests with a segfault in garbage collection caused by pygame cleanup. Disabling GC during tests and running a manual cleanup after each test fixes the issue.