Getting Started
Guides for authoring, running and analysing tests across web automation, API and performance — plus setup, collaboration and release notes.
Platform Architecture (Cloud + Local Agent)
Bitassert combines a cloud platform with a Local Agent on your machine. The cloud stores test assets, queues runs, and saves results; the Local Agent handles real-time local execution and debugging from the UI. Use cloud runs when you need persisted outcomes and shared execution environments. Use the Local Agent while authoring testcases or validating steps before a formal cloud run.
Note:
Local execution is for developing testcases on your machine through the Local Agent. Those runs are not saved in the platform. Only cloud executions are stored and available in Test Results.
Cloud layer
- Stores test assets (testcases, step groups, elements, test data, run configs)
- Orchestrates test runs
- Stores and serves result data
Local Agent layer
- Supports local execution connectivity
- Handles runtime communication channels
- Provides the local execution bridge for test runs initiated from Bitassert, with real-time run and step status reporting
Local vs Cloud execution
Bitassert supports two ways to run Web tests. Choose Local Agent while authoring and debugging; use Cloud for real test runs you want recorded in the project.
| Local Agent | Cloud | |
|---|---|---|
| Purpose | Develop and debug testcases on your machine | Run tests for real execution and reporting |
| Results saved | No — results are not stored in the platform | Yes — saved for future reference in Test Results |
| Where to start | Testcase details → Run → Local Agent | Testcase list or details → Run → Cloud (tag + Test Run Config) |
| Requirements | Local Agent launched and connected | Test Run Config and run tag |
- Local execution — use while building and validating testcases. Step status and responses appear live in the editor; outcomes are not persisted in Test Results.
- Cloud execution — use for scheduled runs, shared environments, and runs you need to track over time. Results appear in Test Results with status, tag, release, and step-level detail.