Getting Started
Set up your first project, connect a server, and run your first discovery and test run. This guide walks you through every step from sign-up to results.
Create an Account
Navigate to app.testops.calimatic.com and click Sign Up. Calimatic Auth handles all identity management, so you can sign in with your existing Calimatic credentials or create a new account with your email address.
Once authenticated, you land on the Dashboard. This is your central hub for projects, servers, test runs, and reports. Your account is automatically assigned to your organization, and any projects you create will be visible to other members of that organization.
Add Your First Project
Go to Projects > New Project from the sidebar. Fill in the following fields:
- Project Name— A human-readable name for your project (e.g., "Calimatic Core").
- Git URL — The SSH or HTTPS clone URL for your repository.
- Default Branch — The branch that discovery and test runs will target by default (usually
mainordevelop). - Framework— Select your project's primary framework (Next.js, .NET, Python, Go, etc.). This tells the discovery engine which scanners to prioritize.
The project slug is auto-generated from the name. You can customize it before saving, but it cannot be changed later. Click Create Project to finish.
Configure a Server
Navigate to Server Pool > Add Worker. Each worker represents a server that TestOps can SSH into to run discovery, tests, and code generation.
You will need to provide:
- SSH Host — The hostname or IP address of your server (e.g.,
192.168.1.100orstaging.yourcompany.com). - SSH User — The user account TestOps will connect as (e.g.,
deploy). - SSH Key — Select a previously uploaded SSH key, or upload a new one. TestOps stores keys encrypted at rest and never exposes the private key material in the UI.
After saving, TestOps will attempt a connection test to verify the credentials. A green status indicator confirms the server is reachable and ready to accept jobs.
Set Up an Environment
Environments link a project to a specific server. Go to your project's settings and click Add Environment. Select the server you configured in the previous step.
Define the working directory where your project lives on the server. This is the absolute path to the repository root, for example:
TestOps uses this path as the base directory for all SSH operations including discovery scans, test execution, and code generation. Make sure the SSH user has read access to the project files and write access if you plan to use test generation.
Run Your First Discovery
Navigate to your project page and click Run Discovery. The discovery engine uses a two-pass architecture:
- Structural Scan— SSHes into the server, scans the codebase, and identifies files, endpoints, models, services, pages, and integrations based on your framework's conventions.
- Semantic Analysis — Uses AI to deeply understand business rules, authentication patterns, data flows, and third-party integrations that static scanning alone would miss.
The result is a complete Feature Inventory— a structured map of everything in your codebase. This inventory powers gap analysis, test generation, and coverage tracking. Discovery typically takes 2–5 minutes depending on project size.
You can re-run discovery at any time. TestOps stores snapshots and shows diffs between runs so you can see exactly what changed.
Trigger a Test Run
Go to Runs > New Run from the sidebar. Select your project and configure the run:
- Test Layers — Choose which layers to execute: unit, integration, system, e2e, smoke, or contract tests. You can select multiple layers for a comprehensive run.
- Environment — Pick the target environment (server) where the tests will run.
- Branch — Optionally override the default branch to test a feature branch.
Click Run to start. The execution engine SSHes into the server, pulls the latest code, seeds test data if configured, and executes the selected test layers. Monitor progress in real-time with live log streaming. Results, pass rates, and coverage metrics appear as soon as the run completes.
Next Steps
You now have a fully operational TestOps setup. Explore the remaining guides to unlock the full power of the platform:
- Discovery Engine — Deep dive into structural scanning and semantic analysis.
- Gap Analysis — Learn about the 39+ automated checks that find what your test suite is missing.
- Test Generation — Generate comprehensive tests from your feature inventory using AI.
- Scheduling & Workers — Set up cron-based schedules and manage your worker fleet.
- Report Publishing — Share test reports with stakeholders via token-based links.