Skip to main content

A wrapper for commands to be run as periodic tasks while reporting on their results/errors to legiond. Intended to be integrated with supervisord, should work well with systemd in theory.

Project description

Testudo

A wrapper for commands to be run as periodic tasks while reporting on their results/errors to legiond. Intended to be integrated with supervisord, should work well with systemd in theory.

Setup & Usage

Installation

testudo can be easily installed with pip:

pip3 install testudo

Configuration

TODO

Usage

The key reference for using testudo is:

testudo --help

Development

Standards

  • Be excellent to each other
  • Code coverage must be at 100% for all new code, or a good reason must be provided for why a given bit of code is not covered.
    • Example of an acceptable reason: "There is a bug in the code coverage tool and it says its missing this, but its not".
    • Example of unacceptable reason: "This is just exception handling, its too annoying to cover it".
  • The code must pass the following analytics tools. Similar exceptions are allowable as in rule 2.
    • pylint --disable=C0103,C0111,W1203,R0903,R0913 --max-line-length=120 testudo
    • flake8 --max-line-length=120 ...
    • mypy --ignore-missing-imports --follow-imports=skip --strict-optional ...
  • All incoming information from users, clients, and configurations should be validated.
  • All internal arguments passing should be typechecked whenever possible with typeguard.typechecked

Development Setup

Using pdm install from inside the repo directory:

pdm install

This will set up a virtualenv which you can always run specific commands with pdm run ....

Development

Testing

All testing should be done with pytest which is installed with the --dev requirements (pdm --dev install ...).

To run all the unit tests, execute the following from the repo directory:

pdm run pytest

This should produce a coverage report in /path/to/dewey-api/htmlcov/

While developing, you can use watchexec to monitor the file system for changes and re-run the tests:

watchexec -r -e py,yaml pdm run pytest

To run a specific test file:

pdm run pytest tests/unit/test_cli.py

To run a specific test:

pdm run pytest tests/unit/test_cli.py::test_cli_basics

For more information on testing, see the pytest.ini file as well as the documentation.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

testudo-0.3.2.tar.gz (22.5 kB view details)

Uploaded Source

Built Distribution

testudo-0.3.2-py3-none-any.whl (20.6 kB view details)

Uploaded Python 3

File details

Details for the file testudo-0.3.2.tar.gz.

File metadata

  • Download URL: testudo-0.3.2.tar.gz
  • Upload date:
  • Size: 22.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.10.6

File hashes

Hashes for testudo-0.3.2.tar.gz
Algorithm Hash digest
SHA256 3ad823bbc3bf9d6a16a04574d03b79dcf811bb2ef67acf6071dab70e81694361
MD5 5cf549605fa6389ed2de5e6e638789cd
BLAKE2b-256 ac8144a8f27fa0a37da49d6f7687a9cb0da74cc000d34f4761557728e59b0945

See more details on using hashes here.

File details

Details for the file testudo-0.3.2-py3-none-any.whl.

File metadata

  • Download URL: testudo-0.3.2-py3-none-any.whl
  • Upload date:
  • Size: 20.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.10.6

File hashes

Hashes for testudo-0.3.2-py3-none-any.whl
Algorithm Hash digest
SHA256 2b61af4d617bece8d25fe3e30251fab086cdb7861d24fb08983d3bfeaef5a252
MD5 3d97e80bbde429fda9019088bab5999d
BLAKE2b-256 4dc8a98bfcae83f9b6dc7b25e8eab83225202e2c88cf3b8cbc1a4ffe863607e4

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page