Concepts
Data types
Boolean
Integer
String
Decimal
Verdict
TimeSpan
DateTime
Loose Time
Loose Date
Enumeration
GUID
Procedure Reference
Data Table Reference
ZapTool Reference
Test Suite Reference
DataSource Reference
Converting data types (Casting)
Devices
Device Entities
Device Browser
Virtual Devices
Value Converters
Reports
New Report
JUnit
FACTS
Printing
Printing from SeqZap Studio
Printing on the command line
Python Procedure
Script File References
Selecting procedure
Steps
Procedure Call
Log
Activation Server
Logging in
Licenses and Machines
Releases
Debugging Mode
User Interface
Help
Getting Support
Script Editing
Inserting steps using the mouse
Inserting steps using the keyboard
Re-arranging/moving steps/procedures/etc.
Re-arranging/moving workbench tools
Script Debugging
Single Stepping
Variable Inspection
Breakpoints
Debug Mode
Keyboard shortcuts
Integrating SeqZap
SeqZap Command Line Interface
Basic operation
Supported arguments and flags
Specifying the command line arguments in a file
Integrating SeqZap with Jenkins
JUnit report
Using --studio to debug scripts
Best Practice
Project Structure
Desired project structure
Bonus features by using this project structure
Overview of project structure
Sharing a workbench between products
Sharing configuration properties
Appendix
3. Party components used in SeqZap
Reporting errors in SeqZap
Describing the error
How is SeqZap running
Data to collect
Known Issues