Regression test enhancement for the Python unittest framework
Writing tests is important (see here). And when it comes to an existing and running application even more. Existing results must at any chance be reproduced (like-for-like tests).
An easy way to add many test cases is by invoking the application and its subroutines many times. But taking notes (and hardcoding) of all results is annoying.
Here regtest might help.
Simply, write routines that invoke our application. The initial run will collect and store return values in files. The next time (and at any time these routines run) the return values will be checked against the stored ones.
To reset a routine simply remove the corresponding file (named accordingly) of stored reference data. The next time the reference data will be rebuild.
1 maintainer
Metadata
1 maintainer
Release files for regtest 0.3.3
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 | Actions |
|---|---|---|---|---|
| regtest-0.3.3.zip | 13.5 kB | Without provenance | Details for regtest-0.3.3.zip |
Release files / regtest-0.3.3.zip
| Download URL | regtest-0.3.3.zip |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0f9fa744b4752ccc74a6c0897f5925ed13e4f2174131962de455ba7615e38c5
|
|
BLAKE2b-256 checksum How to use checksums |
f100ce422855fcde2bf89c8b25b624d8c2add4fede7667df30232620f7a131c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.11
|
Security for regtest 0.3.3
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.
