TIA Portal Test Suite — Automated Testing
Scope
The installed Siemens.Engineering.TestSuite API covers Application Test,
Style Guide, and System Test. These are different execution environments and
must not share safety assumptions.
Reference files
Load ONLY the reference file(s) relevant to the task. Do not load all files at once.
| Reference file |
Load when the task involves |
references/application-test.md |
Application Test sets/cases, PLCSIM execution modes, import, scope, and execution. |
references/style-guide.md |
Style Guide rule sets, import, scope update, and execution. |
references/system-test.md |
System Test cases, OPC UA endpoints/interfaces, import, scope, and execution. |
references/test-results.md |
Recursive result/message interpretation and pass/fail gates. |
Installed V21 root
TestSuiteService service = project.GetService<TestSuiteService>();
ApplicationTestSystemGroup application = service.ApplicationTestGroup;
StyleGuideSystemGroup styleGuide = service.StyleGuideGroup;
SystemTestSystemGroup system = service.SystemTestGroup;
The groups are singular properties. Resolve test sets, cases, and rule sets by
exact name and expected scope; never select .First() or [0].
Executor ownership
Executors are group services:
TestCaseExecutor applicationExecutor =
service.ApplicationTestGroup.GetService<TestCaseExecutor>();
RuleSetExecutor styleExecutor =
service.StyleGuideGroup.GetService<RuleSetExecutor>();
SystemTestCaseExecutor systemExecutor =
service.SystemTestGroup.GetService<SystemTestCaseExecutor>();
Every Run(...) returns TestResults. Apply the recursive result gate from
references/test-results.md; a returned object alone is not a passing test.
Permission and safety enforcement
- V21 introduces the
Edit Test Suite data user right. Require it before importing, deleting, or changing test sets, cases, rule sets, or scope.
- Treat imported test/rule files as untrusted input. Validate the exact file, provenance, intended objects, load options, and resulting identities before saving the project.
ImportOptions.Override and scope replacement are destructive. Require explicit project-write authorization and an inventory of affected objects.- Application Tests execute through PLCSIM. Require explicit simulator-execution authorization and distinguish system-managed from externally managed instances.
- System Tests use OPC UA and may target a live controller or other production endpoint. Require explicit live-operation authorization, the exact OPC UA endpoint/interface, credential/security expectations, and an approved test case. Never assume simulation.
- Style Guide execution is static, but imports and scope changes still mutate the project.
- Do not save the project unless requested. Do not claim success until top-level and nested result states, counts, and messages all pass the result gate.
Evidence boundary
Installed V21 assemblies/XML prove API names, signatures, types, and enum members.
Project permissions, PLCSIM availability/identity, OPC UA reachability/security,
test side effects, and actual results require an authorized runtime test.
1---2name: tia-testsuite3description: TIA Portal V21 Test Suite operations. Use for Application Tests with PLCSIM, Style Guide rules, System Tests through OPC UA, import/scope management, execution, and recursive result evaluation.4license: MIT5---67# TIA Portal Test Suite — Automated Testing89## Scope1011The installed `Siemens.Engineering.TestSuite` API covers Application Test,12Style Guide, and System Test. These are different execution environments and13must not share safety assumptions.1415## Reference files1617Load ONLY the reference file(s) relevant to the task. Do not load all files at once.1819| Reference file | Load when the task involves |20|---|---|21| `references/application-test.md` | Application Test sets/cases, PLCSIM execution modes, import, scope, and execution. |22| `references/style-guide.md` | Style Guide rule sets, import, scope update, and execution. |23| `references/system-test.md` | System Test cases, OPC UA endpoints/interfaces, import, scope, and execution. |24| `references/test-results.md` | Recursive result/message interpretation and pass/fail gates. |2526## Installed V21 root2728```csharp29TestSuiteService service = project.GetService<TestSuiteService>();3031ApplicationTestSystemGroup application = service.ApplicationTestGroup;32StyleGuideSystemGroup styleGuide = service.StyleGuideGroup;33SystemTestSystemGroup system = service.SystemTestGroup;34```3536The groups are singular properties. Resolve test sets, cases, and rule sets by37exact name and expected scope; never select `.First()` or `[0]`.3839## Executor ownership4041Executors are group services:4243```csharp44TestCaseExecutor applicationExecutor =45 service.ApplicationTestGroup.GetService<TestCaseExecutor>();46RuleSetExecutor styleExecutor =47 service.StyleGuideGroup.GetService<RuleSetExecutor>();48SystemTestCaseExecutor systemExecutor =49 service.SystemTestGroup.GetService<SystemTestCaseExecutor>();50```5152Every `Run(...)` returns `TestResults`. Apply the recursive result gate from53`references/test-results.md`; a returned object alone is not a passing test.5455## Permission and safety enforcement56571. V21 introduces the `Edit Test Suite data` user right. Require it before importing, deleting, or changing test sets, cases, rule sets, or scope.582. Treat imported test/rule files as untrusted input. Validate the exact file, provenance, intended objects, load options, and resulting identities before saving the project.593. `ImportOptions.Override` and scope replacement are destructive. Require explicit project-write authorization and an inventory of affected objects.604. Application Tests execute through PLCSIM. Require explicit simulator-execution authorization and distinguish system-managed from externally managed instances.615. System Tests use OPC UA and may target a live controller or other production endpoint. Require explicit live-operation authorization, the exact OPC UA endpoint/interface, credential/security expectations, and an approved test case. Never assume simulation.626. Style Guide execution is static, but imports and scope changes still mutate the project.637. Do not save the project unless requested. Do not claim success until top-level and nested result states, counts, and messages all pass the result gate.6465## Evidence boundary6667Installed V21 assemblies/XML prove API names, signatures, types, and enum members.68Project permissions, PLCSIM availability/identity, OPC UA reachability/security,69test side effects, and actual results require an authorized runtime test.
czarnak