Welcome to Teflo!
What is Teflo?
TEFLO stands for (T est E xecution F ramework L ibraries and O bjects)
Teflo is an orchestration software that controls the flow of a set of testing scenarios. It is a standalone tool written in Python that includes all aspects of the workflow. It allows users to provision machines, deploy software, execute tests against them and manage generated artifacts and report results.
Teflo Provides structure, readability, extensibility and flexibility by :
providing a YAML file to express a test workflow as a series of steps.
enabling integration of external tooling to execute the test workflow as defined by the steps.
Teflo can be used for an E2E (end to end) multi-product scenario. Teflo handles coordinating the E2E task workflow to drive the scenario execution.
Teflo can be used for an E2E (end to end) multi-product scenario. Teflo handles coordinating the E2E task workflow to drive the scenario execution.
What does an E2E workflow consist of?
At a high level teflo executes the following tasks when processing a scenario.
Provision system resources
Perform system configuration
Install products
Configure products
Install test frameworks
Configure test frameworks
Execute tests
Report results
Destroy system resources
Send Notifications
Teflo has following stages
Provision - Create resources to test against (physical resources, VMs etc)
Orchestrate - Configure the provisioned resources (e.g. install packages on them, run scripts, ansible playbooks etc)
Execute - Execute tests on the configured resources
Report - Send or collect logs from the tests run
Notification - Send email/gchat/slack notification during each stage of teflo run or at the end based on the set triggers
Cleanup - Cleanup all the deployed resources.
These stages can be run individually or together.
Teflo follows a plugable architechture, where users can add different pluggins to support external tools Below is a diagram that gives you a quick overview of the Teflo workflow
To learn more about how to set up and use Teflo please check out https://teflo.readthedocs.io/en/latest/
To know how to create a custom plugin check out https://teflo.readthedocs.io/en/latest/developers/development.html#how-to-write-an-plugin-for-teflo
To know about our release cadence and contribution policy check out https://teflo.readthedocs.io/en/latest/developers/development.html#release-cadence
Metadata
Release files for teflo 2.4.1
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 |
|---|---|---|---|---|
| teflo-2.4.1.tar.gz | 135.8 kB | Without provenance | Details for teflo-2.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| teflo-2.4.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for teflo-2.4.1-py2.py3-none-any.whl |
Total release size: 322.0 kB
Release files / teflo-2.4.1.tar.gz
| Download URL | teflo-2.4.1.tar.gz |
|---|---|
| Size | 135.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36741316e3fd5644b46b68dc74838b81cb29890c796f4f316000fcb1ab4f8489
|
|
BLAKE2b-256 checksum How to use checksums |
ec6bb6295afd4735eb25eab82185a29925d443122b8ef997244ab93681861e49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / teflo-2.4.1-py2.py3-none-any.whl
| Download URL | teflo-2.4.1-py2.py3-none-any.whl |
|---|---|
| Size | 186.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f92cbb33b40c8ced81d8b3dcd090b4a86f1a032103b9072fe9c0b0db32f9a74c
|
|
BLAKE2b-256 checksum How to use checksums |
3d7852ff234f622acaaf53ad5305ac114b83c7407eb1597ae6b06e204fa4e86b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for teflo 2.4.1
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.