Multi-vendor test infrastructure
2ot treats verification as a compiler capability: shared suites, runtime-equivalence checks and target-specific runners live alongside the backends they validate.
One test layer across multiple targets
2ot contains shared IEC test harness infrastructure and dedicated suites for multi-vendor behavior. This keeps target comparison in one place instead of scattering validation logic across individual integrations.
Runtime equivalence
The test suite includes runtime-equivalence checks designed to compare behavior across supported targets. That gives the compiler a concrete regression surface for changes that must preserve semantics as code moves between environments.
Vendor-specific runners
Siemens TIA has dedicated runner support, while TwinCAT includes runner and TcUnit integration. Vendor-specific mechanics stay behind the 2ot test layer instead of becoming separate public products.
What the test layer covers
| Area | Purpose |
|---|---|
| multi-vendor | Cross-target verification. |
| runtime equivalence | Behavioral comparison across runtimes. |
| Siemens TIA | Target-specific execution support. |
| TwinCAT | TwinCAT test integration and TcUnit support. |
Built for compiler evolution
As new passes, backends and integrations land, the shared test infrastructure gives 2ot a place to prove both target-specific behavior and cross-vendor consistency.