Allow pytest discovery to find and run Python tests

[cclauss]

• Upgrade NumPy and other Python dependencies #30292 says that dependencies are being pinned to out-of-date versions. Let's use pytest discover to see which Python tests will be found and see what dependencies they require, and if they will pass with the current versions of those dependencies.

https://docs.pytest.org/en/stable/explanation/goodpractices.html#conventions-for-python-test-discovery

Test results: https://github.com/ArduPilot/ardupilot/actions/runs/16271173917/job/45938928611?pr=30361

% pytest --config-file=tests/pytest-whole-repo.toml

============================= test session starts ==============================
platform linux -- Python 3.14.0, pytest-8.4.2, pluggy-1.6.0
rootdir: /home/runner/work/ardupilot/ardupilot/tests
configfile: pytest-whole-repo.toml
collected 59 items

tests/Tools/autotest/unittest/annotate_params_unittest.py .............. [ 23%]
..........                                                               [ 40%]
tests/Tools/autotest/unittest/extract_param_defaults_unittest.py ....... [ 52%]
...........                                                              [ 71%]
tests/Tools/scripts/param_check_unittests.py ...........                 [ 89%]
tests/test_pre_commit_copyright.py ......                                [100%]

============================== 59 passed in 2.83s ==============================

[peterbarker]

Just a note that upgrading numpy won't necessarily kill in-tree tools, but most definitely kills MAVProxy which is usually run in the same venv. This does suck.

[cclauss]

Status:

1. --ignore=modules/gtest DRAFT: gtest needs an upgrade for Python 3 #30426
   • Currently contains Python 2 code that would crash Py3. Probably always --ignore.
2. --ignore=modules/mavlink/pymavlink/generator/C/test/posix/sha256_test.py
   • Py2 dead code deleteed in generator: Remove dead code sha256_test.py pymavlink#1081
3. --ignore=modules/mavlink/pymavlink/tests/test_wp.py
   • Mismatch in number of arguments! -- Help needed.
4. --ignore=modules/waf/playground
   • https://gitlab.com/ita1024/waf/-/merge_requests/2389
5. --ignore=Tools/autotest/test_build_options.py
   • Fixed in autotest: Fall back to relative imports in pytest discovery #30444 and here
6. --ignore=Tools/autotest/test_param_upgrade.py
   • Fixed in autotest: Fall back to relative imports in pytest discovery #30444 and here
7. --ignore=Tools/FilterTestTool/run_filter_test.py
   • Fixed in Tools: Fix run_filter_test.py to not confuse pytest discovery #30443 - Probably always --ignore
8. --ignore=Tools/ros2/ardupilot_dds_tests/test
   • pre-commit: Add a job that runs ament_pep257 Tools/ros2 #30449
   • Tools: Add pre-commit hook to check copyright in ros2 files #30598
   • Probably always --ignore because designed to run in the Docker image ardupilot/ardupilot-dev-ros.

[cclauss]

Based on the "too wildcardy" discussion in today's EU dev call, we should stop using --ignore to constrain the pytest discovery rules and instead use testpaths to focus pytest only on paths that are known to contain runnable tests.

testpaths = [
    "tests",
    "Tools/autotest/unittest",
    "Tools/scripts",
]

Also,

• tests: README.md caution about pytest run in GitHub Actions #30666

[peterbarker]

Based on the "too wildcardy" discussion in today's EU dev call, we should stop using --ignore to constrain the pytest discovery rules and instead use testpaths to focus pytest only on paths that are known to contain runnable tests.

testpaths = [
    "tests",
    "Tools/autotest/unittest",
    "Tools/scripts",
]

Also,

* [tests: README.md caution about pytest run in GitHub Actions #30666](https://github.com/ArduPilot/ardupilot/pull/30666)

testpaths should allow us to get something in quite quickly. There are many PRs in your checklist in here which are stalled/stale, so perhaps pushing ahead on testpaths here would be a good idea?

[cclauss]

59 passed in 2.83s -- Ready for review.

Can a repo maintainer please rerun the failing test?