pytest-testinfra VS robotmk

Compare pytest-testinfra vs robotmk and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
pytest-testinfra robotmk
2 1
2,320 52
0.7% -
7.6 9.6
7 days ago 7 days ago
Python Rust
Apache License 2.0 GNU General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of pytest-testinfra. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-31.

robotmk

Posts with mentions or reviews of robotmk. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-27.
  • Real-Time Performance Monitoring Software
    3 projects | /r/networking | 27 Jul 2022
    We are using checkmk to monitor 1000s of locations in terms of reachability and performance. Basically you use the checkmk (www.checkmk.com) server as a central site that pings your network devices and your servers (both is important since a slow server doesn't mean "the network is so slow(tm)" ) In Checkmk you get nice graphs but you can also export your data to grafana (which is what we do) to build a smokeping like expirience. Smokeping is a nice tool, but it's rather old and does not scale too well. Checks from your network devices can be implemented using ipsla (cisco?). Theres a plugin for that: https://checkmk.com/de/integrations/cisco\_ip\_sla. If you want to monitor stuff from a (near) user perspective: Check MK supports a distributed setup that allows you to place sensors in differenent locations (if you don't want to implement the full end-to-end monitoring using something like Robot-Framework (https://github.com/simonmeggle/robotmk). If you want deeper network visibility then you could pair checkmk with ntopng (https://www.ntop.org/products/traffic-analysis/ntop/). This way you'll get a lot more than plain RTT and network interface load like ipfix, dpi, *flow, etc...

What are some alternatives?

When comparing pytest-testinfra and robotmk you can also consider the following projects:

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.

infracheck - Incredibly elastic and lightweight health check endpoint to cover ANY CASE, including infrastructure as well as applications

dredd - Language-agnostic HTTP API Testing Tool

check-zfs-replication - This script checks yout ZFS replication an generates reports in different flavours or can act as checkmk agent plugin (local check).

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.

Nagstamon - Nagios status monitor for your desktop.

RHCA-study-notes - Red Hat Certified Architect personal study notes.

prometheus - The Prometheus monitoring system and time series database.

Puppet-Guide - Puppet Guide

spidermon - Scrapy Extension for monitoring spiders execution.

faker - Faker is a Python package that generates fake data for you.

tvl - Docker setup with common work tools