opsdroid VS pytest

I decided to add to an open source Python based chat bot called opsdroid. I was initially worried about whether I had what it takes to do another code contribution on time, learning an entirely new project is always daunting. I brought it up to my professor David and he encouraged me to go for it, an honest attempt at something beyond my capabilities would be taken into consideration for the final project and to "be fearless. don't let code push you around.

This time I helped them migrate to aioredis 2.0 (and then used the experience I've got to do the same in my own project), and to set up proper docker images builds: https://github.com/opsdroid/opsdroid/pull/1835 https://github.com/opsdroid/opsdroid/pull/1836

Have a look at https://opsdroid.dev/ it has Slack support, you can then bridge Slack/Discord with matterbridge or something to get functionality from both sides.

https://github.com/opsdroid/opsdroid An open source chat-ops bot framework

In this blog post I want to demonstrate how my lab equipment such as a lab power supply or a digital multimeter (DMM) have been integrated into some pytest-based tests. Would love to get your feedback and thoughts! 🚀

Pytest: is a third-party testing framework that supports fixtures, parameterized testing, and easy test discovery while having room to add plugins to extend its functionality.

Next, you need to install a testing framework that will be used for performing unit testing in your project. Several testing frameworks are available depending on the programming language used to create an application. For example, JUnit is commonly used for Java apps, pytest for Python apps, NUnit for .NET apps, Jest for JavaScript apps, and so on. We’ll use the Jest framework for this tutorial since we are using JavaScript.

Yea, read through the pytest docs.

I absolutely agree about fixtures-as-arguments thing. Ward does this a lot better, using default values for the fixture factory. There's a long issue on ideas to implement something like that as a pytest plugin (https://github.com/pytest-dev/pytest/issues/3834), but it seems the resulting plugin relies on something of a hack.

I recommend writing a few tests. py.test makes that quite simple:

Since ITK's inception in 1999, there has been a focus on engineering practices that result in high-quality software. High-quality scientific software is driven by regression testing. The ITK project supported the development of CTest and CDash unit testing and software quality dashboard tools for use with the CMake build system. In the Python programming language, the pytest test driver helps developers write small, readable scripts that ensure their software will continue to work as expected. However, pytest can only test Python scripts by default, and errors in untested computational notebooks are more common than well-tested Python code.