- Erste Schritte
- Projektmanagement
- Dokumente
- Arbeiten mit der Analyse der Änderungsauswirkungen
- Erstellen von Testfällen
- Assigning test cases to requirements
- Klonen von Testfällen
- Exportieren von Testfällen
- Linking test cases in Studio to Test Manager
- Delete test cases
- Manuelle Testfälle
- Importieren manueller Testfälle
- Dokumentieren von Testfällen mit Task Capture
- Parameter
- Anwenden von Filtern und Ansichten
- Importieren von Orchestrator-Testsätzen
- Creating test sets
- Assigning test cases to a test set
- Aktivieren der Aktivitätsabdeckung
- Konfigurieren von Testsätzen für bestimmte Ausführungsordner und Roboter
- Überschreiben von Parametern
- Klonen von Testsätzen
- Exportieren von Testsätzen
- Anwenden von Filtern und Ansichten
- Ausführen von manuellen Tests
- Ausführen automatisierter Tests
- Ausführen von Testfällen ohne Testsatz
- Ausführen gemischter Tests
- Erstellen von ausstehenden Ausführungen
- Erzwingen einer Ausführungsreihenfolge
- Erneutes Ausführen von Testausführungen
- Planen von Ausführungen
- Fehlerbehebung bei automatisierten Ausführungen
- Performance Testing Virtual Users Bundle
- Performance testing - usage example
- Platform Units and infrastructure costs
- Additional licenses
- Creating automated tests
- Executing performance scenarios
- Known limitations for performance testing
- Best paractices for performance testing
- Troubleshooting performance testing
- Suche mit Autopilot
- Projektvorgänge und Dienstprogramme
- Test Manager-Einstellungen
- ALM Tool-Integration
- API-Integration
- Fehlersuche und ‑behebung

Test Manager-Benutzerhandbuch
A Performance Testing Virtual Users Bundle is a licensing package which provides a fixed number of Virtual User units (VU units), which are consumed when running performance tests across Desktop, Web UI, and API automations.
Each Virtual Users Bundle includes 2,500 VU units with predefined usage ratios, allowing customers to flexibly allocate capacity across different automation types without purchasing separate licenses.
A Virtual Users Bundle includes 2,500 VU units which can be used across all projects in the Test Manager tenant where the bundle is assigned.
Usage ratios define how VU units are consumed depending on the automation type: 1 Desktop VU = 10 Web UI VUs = 100 API VUs
Check the following examples for using VUs:
- Running 10 Desktop virtual users consumes 1,000 VU units.
- Running 100 Web UI virtual users consumes 1,000 VU units.
- Running 500 API virtual users consumes 500 VU units.
Performance testing runtimes are robot runtimes in Orchestrator, dedicated exclusively to performance-testing jobs. Each Performance Testing Virtual Users Bundle provides 250 runtimes, which must be configured within machine templates in Orchestrator and are required for running tests on on-premises robots (machines). They are delivered in large quantities to ensure customers always have sufficient parallel capacity for large-scale test execution.
Serverless cloud robots consume Platform Units instead.
When the total VU units required by all active performance scenarios are within the available Virtual Users Bundle capacity assigned to the tenant.