Skip to content
#

rf

robotframework logo

Robot Framework is an open source, easy to learn, and easy to use, yet powerful, and extendable, generic automation framework for software testing and RPA (robotic process automation). While it's original purpose was to support acceptance testing and acceptance test driven development (ATDD) of embedded software at Nokia Networks back in 2005, nowadays it is also widely used for automation of integration tests and end-to-end tests in desktop, web, and mobile development. You can use it to automate GUI based applications as well as REST, RPC, SOAP and other API, and protocol based testing. Due to it's text based nature and cli tools RF is a perfect match for agile and DevOps, and DevSecOps driven projects striving to succeed in continuous testing. It integrates very well with open source and commercial CI/CD solutions like Jenkins, CircleCI, Github Actions, and Azure Pipelines - just to name a few. It is also developer friendly and can easily be versioned with Git, and used with Docker and other container and virtualisation technologies to support building and maintaining of scalable (test) environments following the configuration as code or infrastructure as code approach. RF can be used in projects of any technology stack, and runs on any infrastructure (Windows, Mac, Linux, cloud) - it is stack and infrastructure agnostic.

Here are 174 public repositories matching this topic...

rct
rct commented Feb 10, 2020

Acurite TXR, 5n1, 6045 and possibly others like the new Atlas weather station use parity in addition to checksums for integrity checking.

Currently the parity isn't verified, it's only looked at in verbose mode.

I've noticed I seem to get messages for non-existent devices from time to time. I suspect the message is mangled but the checksum still passes. The parity check in addition to the

You can’t perform that action at this time.