Instrumental automatically instruments your code to add function calls that reveal execution characteristics. Instrumental can then monitor execution of your code and report back to you on how your source was executed.
When you run a script with Instrumental, it will tell you which decisions and conditions haven’t been fully exercised. So for a decision in an if statement, it will tell you if the decision only ever evaluated True or False. Instrumental will also tell you if the conditions in boolean decisions (and, or) were ever executed both True and False.
As an example: if you usually say
python setup.py nosetests
you can say
instrumental -rS -t <packagename> setup.py nosetests
where packagename is the name of your project’s top-level package.
For more information visit the Instrumental documentation.
Announcements and discussion about instrumental can be found on the “python-instrumental-discuss” google group.
Please file bug reports and enhancement requests on bitbucket.
1 maintainer
Metadata
1 maintainer
Release files for instrumental 0.5.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 | |
|---|---|---|---|
| instrumental-0.5.3.tar.gz | 148.8 kB | Details |
Release files / instrumental-0.5.3.tar.gz
| Download URL | instrumental-0.5.3.tar.gz |
|---|---|
| Size | 148.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
472d3588d3e4b29238531143114d5a481ba077c62ed97aa5d77aee572f00a8b8
|
|
BLAKE2b-256 checksum How to use checksums |
30035872f41363794774d9f71359b12258e709a825125ce3f261adafe07d956d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
