diff options
| author | Eli Schwartz <eschwartz@archlinux.org> | 2022-03-16 18:36:25 -0400 |
|---|---|---|
| committer | Eli Schwartz <eschwartz@archlinux.org> | 2022-03-16 18:39:02 -0400 |
| commit | 4b0c0810df8e0fae9529d879539b8926b5b278a3 (patch) | |
| tree | 31f11e73e0141678e8f60e4c16ba492215733f91 /test cases/python/8 different python versions/test.json | |
| parent | ff844f3a1fd0cac31e2f61add59393b16548c97c (diff) | |
| download | meson-4b0c0810df8e0fae9529d879539b8926b5b278a3.tar.gz | |
unittests: convert python tests to project tests
Perhaps when this test case was originally created, project tests could
not use a matrix of options? This is certainly possible today, so don't
write special unittest handling for this instead.
This adds proper visibility into what gets run and what doesn't. Now we
know which python executables got tested and which got skipped.
Diffstat (limited to 'test cases/python/8 different python versions/test.json')
| -rw-r--r-- | test cases/python/8 different python versions/test.json | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/test cases/python/8 different python versions/test.json b/test cases/python/8 different python versions/test.json new file mode 100644 index 000000000..fe75a1c26 --- /dev/null +++ b/test cases/python/8 different python versions/test.json @@ -0,0 +1,13 @@ +{ + "matrix": { + "options": { + "python": [ + { "val": null }, + { "val": "python2" }, + { "val": "python3" }, + { "val": "pypy" }, + { "val": "pypy3" } + ] + } + } +} |