📊 Visualize Your Testing Workflows with TERN

TERN is a scalable automation system designed to simplify and accelerate integration testing using BPMN-based workflows. TERN enables teams to define, execute, monitor, and validate integration tests visually, reducing manual effort and improving reliability in network-aware test environments.

TERN is intended for complex lab setups where products, virtual machines, hardware appliances, and supporting infrastructure must be tested together under controlled conditions. The platform combines workflow orchestration, asset-aware execution, and network preparation into a single operational environment.

• Visual BPMN Designer - create, edit, and manage automation workflows through a visual scenario-based interface.

• Monitoring & Analytics - track execution status, review logs, investigate incidents, and analyze operational metrics in context.

• Multi-System Integration - connect virtual machines, external systems, and hardware assets to simulate real-world product interactions.

• Network Context Provisioning - prepare isolated and configurable network environments required for running integration tests in real or virtualized lab conditions.

• Asset Lifecycle Management - register assets, manage their availability, deploy product virtual machines, and prepare them for use in test scenarios.

At a high level, TERN supports the following flow:

1. Define a test scenario as a workflow of executable modules.
2. Activate the scenario and prepare the required assets.
3. Launch a task based on the selected scenario.
4. Let the system resolve the required variables, asset mapping, and network context.
5. Monitor execution through statuses, logs, incidents, and metrics.
6. Analyze the result and reuse the scenario for future runs.

• Scenario - a reusable test workflow describing what should be executed.
• Task - a concrete run of an active scenario.
• Asset - a product, external system, virtual machine, hardware node, or variable container used during execution.
• Deploy Operation - a process that creates a new product VM asset.
• Incident - a separate object for investigating failures and abnormal execution results.

• Validate interactions between several security products in one test environment.
• Prepare isolated network context for repeatable integration tests.
• Reuse the same scenario with different assets and configurations.
• Deploy and configure new product virtual machines for upcoming test runs.
• Investigate failed runs using logs, incidents, and contextual monitoring.

✍️ Save this repository so you don't miss our first release!