didak
Python is a basic test case runner, that simulates input and verifies the whether the final output is correct.
Requirements
Didak uses the following packages:
- arkivist
- autopep8
- maguro
Usage
Install the latest didak package, upcoming versions might introduce unannounced changes, so a virtual environment is a must have before installation.
pip install -U didak
To integrate didak into your Python codes, check the code snippet below:
import didak
didak.didak(directory, testcase, identifier, sensitive=0, unzip=0, convert=0, loops=99, reset=0)
CLI Usage
# usage: runner [-h] -d directory -t testcase [-i identifier] [-s sensitive] [-u unzip] [-c convert] [-l loops] [-r reset]
py runner.py -d "<path_to_files>" -t "<path_to_testcase>" -i "<keyword>" -s 1 -u 1 -c 1 -l 99 -r 1
-d <path>- Full path of the dirctory containing the files to execute.-t <*.txt>- Path to test case file-u <0>- Unzip/extract ZIP files (0-1; default = 0)-c <0>- Convert Jupyter notbooks to Python file (0-1; default = 0)-i <keyword>- Unique keyword found on files to execute-s <0>- Case-sensitivity (0-1; default = 0)-l <99>- Looping / max recursions (1-9999; default = 99)-r <0>- Reset analytics before execution (0-1; default = 0)
Test Case
Is used to fill in expected input and function parameters before execution and verifying of expected output. ** Template*
"Keyword1", "keyword1", "keyword 1" = value1
"Keyword2", "keyword2", "keyword 2" = value1
...
"Keyword3", "keyword3", "keyword 3" = value1
---
"Result1", "result1", "result 1"
"Result2", "result2", "result 2"
...
"Result3", "result3", "result 3"
Sample
"keyword1", "key" = "name"
"abcde", "abc" = 23.7
...
"qwerty", "qwe" = False
---
"Hello, name!", "hello, name!"
"76.87", "76.9", "77"
Did you know?
The repository name didak was inspired from the words deduce and Didache; deduce means to arrived at a consluion by reasoning, while Didache is a manuscript in the Christain theological literature.
Metadata
Release files for didak 1.0.28
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 |
|---|---|---|---|---|
| didak-1.0.28.tar.gz | 18.9 kB | Without provenance | Details for didak-1.0.28.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| didak-1.0.28-py3-none-any.whl | Python 3 | none | any | Details for didak-1.0.28-py3-none-any.whl |
Total release size: 28.0 kB
Release files / didak-1.0.28.tar.gz
| Download URL | didak-1.0.28.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71db86e7cfb52d34cbed93acbc2127637061a019443f82c49969e7aa22afc4f0
|
|
BLAKE2b-256 checksum How to use checksums |
7e420ef39e704c5b72bf8a10d5fa0c8699ba727d2826af04e7e70c2596c34b88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Release files / didak-1.0.28-py3-none-any.whl
| Download URL | didak-1.0.28-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c13f042990e5d95d3f757b04d7adf6486d1ab3a3a7c9aad1b08fd197ace2830
|
|
BLAKE2b-256 checksum How to use checksums |
944bda3be138f3766870673e3d4cf9626005980b4e8eb149e3a1f1a4f103da2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Security for didak 1.0.28
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.