Automated Testing
Posted: 20 Oct 2017, 09:16
Hi,
I had a little chat with sven about automated testing. Let's say you'd upgrade raspbian and want to know whether your rev pi environment is still fully functional.
Today we at erminas already have a test program that would test if inputs and outputs work as desired. We use a an environment where DIO Inputs are wired to the outputs (of another PI) and vice versa. This way we can simulate machine signals.
The thing sven and I thought about is his python lib. Of course unit testing is valuable. We could create inputs, outputs, counters, virtual devices by software. The important question is, whether virtual testing is sufficient. Does it work with mocks or we should also test the hardware.
For the DIO we could wire inputs to outputs for testing. Of course the range of modules is quite huge. I guess Kunbus already has something for this. So what can users do to automatically test their environments?
I had a little chat with sven about automated testing. Let's say you'd upgrade raspbian and want to know whether your rev pi environment is still fully functional.
Today we at erminas already have a test program that would test if inputs and outputs work as desired. We use a an environment where DIO Inputs are wired to the outputs (of another PI) and vice versa. This way we can simulate machine signals.
The thing sven and I thought about is his python lib. Of course unit testing is valuable. We could create inputs, outputs, counters, virtual devices by software. The important question is, whether virtual testing is sufficient. Does it work with mocks or we should also test the hardware.
For the DIO we could wire inputs to outputs for testing. Of course the range of modules is quite huge. I guess Kunbus already has something for this. So what can users do to automatically test their environments?