Run a series of test invocation making sure each test case works with both 'pytest' and 'python -m pytest' over all working directories between the project root and the directory containing the test script.
├─ src
│
│<-- # run selected __main__'s from this working directory
│
│ └─ __init__.py
│ └─ foo.py
│ ├─ bar
│ │ └─ __init__.py
│ │ └─ bar.py
│ │
│ │<-- # run selected __main__'s from this working directory
│ │
│ └─ run_foo_main.py
│ └─ run_bar_main.py
│
│<-- # run selected test cases from this working directory
│
├─ tests
│ │
│ │<-- # run selected test cases from this working directory
│ │
│ └─ test_foo.py
│ └─ bar
│ │<-- # run selected bar test cases from this working directory
│ │
│ └─ test_bar.py
└─ setup.py
Your run_all_my_tests.py:
from run_all_the_tests import TestCasePath, TestCase, Group, TestType
if __name__ == '__main__':
project_path: PurePath = Path(__file__).absolute().parent.parent
def gen_test_case_path(test_case: str) -> TestCasePath:
return TestCasePath(project_path, PurePath(test_case))
all_test_cases: Tuple[TestCase, ...] = (
TestCase.gen_test_case(gen_test_case_path('tests/test_foo.py')),
TestCase.gen_test_case(gen_test_case_path('tests/bar/test_bar.py')),
)
run_all_tests(all_test_cases)
Each set of tests are run in parallel within Group.ONE. Designate
tests to run within non-conflicting groups of parallel runs by assigning
all test cases that can run without conflict to the same Group.
all_test_cases: Tuple[TestCase, ...] = (
TestCase.gen_test_case(gen_test_case_path('tests/test_foo.py')),
TestCase.gen_test_case(gen_test_case_path('tests/bar/test_bar.py'), Group.TWO),
)
TestCase.gen_test_case() also supports the following agrs:
pytest_filter: str = None
:param pytest_filter: pytest -k string
test_types: Tuple[TestType, ...] = TestType.all_test_types()
:param test_types: for exceptional situations, limit a TestCase to run for limited set of TestType's
Metadata
Release files for run-all-the-tests 0.1.21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| run-all-the-tests-0.1.21.tar.gz | 9.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| run_all_the_tests-0.1.21-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.6 kB
Release files / run-all-the-tests-0.1.21.tar.gz
| Download URL | run-all-the-tests-0.1.21.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86ca2252aa50f7a18a41558213a001ee16ea1e98bd3aaaf7aadcd8c54481d0d1
|
|
BLAKE2b-256 checksum How to use checksums |
ae5f37f4e20938dbf0a37ec6142c1442da4a277c75dd0955acee09a9dd9e5bb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.0b2 CPython/3.7.9 Darwin/19.6.0
|
Release files / run_all_the_tests-0.1.21-py3-none-any.whl
| Download URL | run_all_the_tests-0.1.21-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5dcf22816e9695ab6df5a84fbff75d8d41602439be07339c44bd10b4d19184f0
|
|
BLAKE2b-256 checksum How to use checksums |
5937e1c0f819a53fb6c6c79ee068b1469c9c81abaae1e820b320dbdbee404730
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.0b2 CPython/3.7.9 Darwin/19.6.0
|
Security for run-all-the-tests 0.1.21
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.