pytest-testinfra
coveragepy
pytest-testinfra | coveragepy | |
---|---|---|
2 | 7 | |
2,325 | 2,849 | |
0.5% | - | |
7.6 | 9.6 | |
9 days ago | 6 days ago | |
Python | Python | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pytest-testinfra
-
The Uncreative Software Engineer's Compendium to Testing
Testinfra: is a testing framework for infrastructure used to test system configurations and infrastructure as code.
-
Help creating a custom TestInfra module
GitHub: pytest-dev/pytest-testinfra - Issue #660
coveragepy
-
An Introduction to Testing with Django for Python
Coverage.py is the go-to tool for measuring code coverage of Python programs. Once installed, you can use it with either unittest or pytest.
-
The Uncreative Software Engineer's Compendium to Testing
Code Coverage Analysis assess the code portions tested by the current test suites without altering the code.
-
Slipcover: Near Zero-Overhead Python Code Coverage
The PLASMA lab @ UMass Amherst (home of the Scalene profiler) has released a new version of Slipcover, a super fast code coverage tool for Python. It is by far the fastest code coverage tool: in our tests, its average slowdown is just 5% (compare to the widely used coverage.py, average slowdown 218%!). The latest release performs both line and branch coverage with virtually no overhead. Use it to dramatically speed up your tests and continuous integration!
-
Unit Tests - what’s the point?
Tests ensure the tested behavior is maintained. It's up to the developers to write tests with sufficient coverage. Determining which lines of code on your project are covered by tests is easily quantifiable using tooling. E.g. https://coverage.readthedocs.io/
-
How to make Django package smaller for Serverless deployment
Taking the idea further, if you build robust tests for your API, you could use a dynamic code analyzer like coverage or figleaf to identify and delete unused functions.
-
Comparison of Python TOML parser libraries
coverage
-
New Ways to Be Told That Your Python Code Is Bad
FWIW, ternary expressions aren't properly detected by coverage: https://github.com/nedbat/coveragepy/issues/509
What are some alternatives?
robotmk - Robotmk - the Robot Framework integration for Checkmk
global-chem - A Knowledge Graph of Common Chemical Names to their Molecular Definition
allure-docker-service - This docker container allows you to see up to date reports simply mounting your "allure-results" directory in the container (for a Single Project) or your "projects" directory (for Multiple Projects). Every time appears new results (generated for your tests), Allure Docker Service will detect those changes and it will generate a new report automatically (optional: send results / generate report through API), what you will see refreshing your browser.
slipcover - Near Zero-Overhead Python Code Coverage
dredd - Language-agnostic HTTP API Testing Tool
Zappa - Serverless Python
eLog - Log your errors to Notion natively in Python, or externally from any other language. Easy set up, then track of what's occuring and when it's fixed.
pytomlpp - A python wrapper for tomlplusplus
RHCA-study-notes - Red Hat Certified Architect personal study notes.
flit - Simplified packaging of Python modules
Puppet-Guide - Puppet Guide
toml - Python lib for TOML