Case study · TestOS
After every PLC program change it should be clear whether sequences, signals, safety conditions and communication still behave correctly. TestOS turns this into a repeatable test process instead of manual checking by feeling.
PLC projects change during development, commissioning and service. Without repeatable tests it is difficult to prove that a new change has not broken an existing function.
TestOS links BDD test cases with execution on the PLC system. Scenarios are managed in Squash TM, source code and configuration are stored in Gitea, and Jenkins starts repeatable test runs.
Instead of a one-time manual check, the project gets a test framework that can be reused after every program, wiring or configuration change.
Concrete result
Test cases are documented so they can be repeated later.
PLC changes are checked with the same method, not only manual inspection.
Reports improve communication between development, commissioning and service.
The project gets a base for further automated testing.
Send a description of the PLC system, signals and typical scenarios you want to verify.
