TestOS for PLC testing
A platform for automated testing of PLC programs, functions and scenarios. TestOS is used as a test runner that connects to the PLC, executes test cases and prepares test results.
Services
Custom software tools
We develop practical technical tools for automation, testing, data conversion and project support. The focus is on solutions that reduce manual work, improve traceability and support more reliable project execution.
BDD testing with open-source tools
Integration of Squash TM for requirements and test cases, Jenkins for execution and Gitea for local source control. Built for repeatable testing of automation projects.
VC4 → mappView converter
A Python tool with a graphical interface for structured migration of B&R VC4 visualizations into mappView files and a project structure prepared for further work in Automation Studio.
Custom technical utilities
Small engineering applications for file preparation, data conversion, report generation, project checks and daily automation engineering support.
Media
Visual examples
Examples show how Bcode tools support PLC testing, visualization conversion and automation project workflows.
TestOS testing
Checking PLC scenarios, wiring and repeatable test cases.
B&R GUI Converter
A tool for faster migration of VC4 visualizations into mappView structure.
TestOS
Automated PLC testing
TestOS is intended for testing PLC programs, functions and sequences in repeatable scenarios. It can be used with a local development infrastructure where requirements, test cases, source control, project builds and test results are connected into one workflow.
Testing PLC functions in realistic scenarios
Checking variable values before and after a test step
Regression testing after program changes
Sequential or cyclic test execution
Reports and test result overview
Useful for wiring checks and HIL approaches
Typical integration
Squash TM + Jenkins + Gitea + TestOS
Squash TM handles requirements and BDD test cases, Jenkins handles execution, Gitea handles versioning, and TestOS connects to the PLC, runs the tests and prepares the results.
1. Define requirements and test cases
2. Build and deploy the project
3. Execute tests on the PLC system
4. Results, reports and regression control
B&R GUI Converter
VC4 to mappView, faster and more repeatable
For existing B&R VC4 visualizations, we develop a converter that supports migration to mappView. The goal is to reduce manual work, keep names and references aligned, and prepare a basic file structure for further work in Automation Studio.
The converter is especially useful in repetitive projects where multiple existing screens need to be moved into a newer environment without rebuilding everything completely by hand.
What you gain
Less manual work when moving from VC4 to mappView
A more consistent structure of generated files and references
Faster preparation of a base for further development in Automation Studio
Better consistency of names, bindings and references across artifacts
A repeatable starting point for converting similar screens
Useful support for upgrading older B&R visualizations
Typical workflow
1. Import an existing VC4 .page or .layout file
2. Prepare page, content, binding and Visualizat structure
3. Generate the required Package.pkg files
4. Continue adjustment and integration inside the mappView project
Do you have repetitive manual work in a project?
We can prepare a custom tool for testing, data conversion, file generation or reporting.