# Steps for Successful Onboarding

SeaLights supports three onboarding methods—**CI/CD-Integrated**, **CD-Only**, and **Standalone**—to fit a range of environments, team structures, and onboarding phases. Regardless of the method, the goal is to report accurate code coverage and test insights to the SeaLights dashboard with minimal disruption.

This guide is intended for **DevOps engineers**, **QA leads**, and **decision makers** seeking to understand the onboarding scope and required resources.

## Typical setup for CI/CD <a href="#typical-setup-for-ci-cd" id="typical-setup-for-ci-cd"></a>

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2FoeXak18lxrIMG4uMHwnv%2FScreenshot%202025-06-23%20at%2014.03.32.png?alt=media&#x26;token=25e2a905-cda7-44d7-8ce4-5aa39867e547" alt=""><figcaption></figcaption></figure>

## Onboarding Approaches <a href="#onboarding-approaches" id="onboarding-approaches"></a>

<table data-header-hidden><thead><tr><th width="189.765625">Onboarding Approach</th><th width="343.8046875">Description</th><th>Why choose this approach</th></tr></thead><tbody><tr><td><strong>CI/CD-Integrated Setup</strong><br><strong>(Recommended)</strong></td><td><p>The most scalable and sustainable method. SeaLights is integrated directly into your CI/CD pipeline to automatically analyze your application and collect coverage and test data during every build and test cycle.</p><p>Use shell commands to instrument builds and report test coverage. Any CI/CD tool that supports command execution is compatible: GitHub Actions, GitLab CI, Azure DevOps (ADO), Jenkins...</p></td><td><ul><li>Seamless integration with daily workflows</li><li>High automation and low ongoing effort</li><li>Supports multiple build/test environments</li></ul></td></tr><tr><td><strong>CD-Only Setup</strong><br><strong>(Intermediate, Java/.NET Only)</strong></td><td><p>An efficient intermediate option that allows onboarding without modifying the CI system — ideal when CI ownership is separate or integration is limited to QA/test environments.</p><p>The SeaLights <strong>CD agent is deployed directly on the application under test</strong>, where it scans and instruments the artifact for coverage collection. It supports executing one or more test types in series, including manual tests or tests running from different machines.</p><p><mark style="color:orange;"><strong>Currently available for Java and .NET applications only</strong></mark></p></td><td><ul><li>Fast time-to-value without CI changes</li><li>Useful when Dev/QA/DevOps teams operate in silos</li><li>Recommended when SeaLights is used only in testing stages</li></ul></td></tr><tr><td><strong>Standalone Setup</strong><br><strong>(Initial, Developer-Local)</strong></td><td><p>Ideal for <strong>early onboarding</strong> or a proof-of-concept (POC) phase, this setup is typically performed on a <strong>developer’s local machine</strong> or a dedicated test environment.</p><p>It enables teams to manually run SeaLights commands or automate them using simple scripts, providing a flexible way to validate integration and gather initial results without involving the CI/CD pipeline.</p><p>This setup is often used as a preliminary step before moving to full CI/CD or CD-only integration. The same commands are reused later—only the parameter values are adapted, usually by injecting environment variables dynamically in CI/CD systems.</p></td><td><ul><li>Minimal setup and no CI/CD involvement</li><li>Ideal for validating the configuration early</li><li>Recommended as a temporary, local test setup</li></ul></td></tr></tbody></table>

## Required Personnel, Knowledge & Permissions <a href="#required-personnel-knowledge-and-permissions" id="required-personnel-knowledge-and-permissions"></a>

It is critical to identify the right project team and ensure their availability for the success of the onboarding project. The following personnel must be available with approved time allocation to ensure an effective and seamless progress:

<table data-header-hidden><thead><tr><th width="272.0625">Role</th><th>Responsibility</th></tr></thead><tbody><tr><td>DevOps/Admin (CI/CD)</td><td>Configure pipelines; access CI jobs and working directories</td></tr><tr><td>QA or CD Environment Owner</td><td>Access to the application under test, including deploy/test environments (CD-only)</td></tr><tr><td>Developer (Standalone)</td><td>Local admin rights to run onboarding commands</td></tr><tr><td>Network/Security contact</td><td>Ensure outbound HTTPS traffic is allowed to SeaLights endpoints</td></tr><tr><td>Application Expert (POC)</td><td>Familiar with app architecture, packages, and testing workflows</td></tr></tbody></table>

{% hint style="success" %}
To ensure a smooth and efficient onboarding experience, we highly recommend all project team members begin with our dedicated **E-Learning Portal**: [Tricentis Academy - SeaLights Courses](https://academy.tricentis.com/pages/105/tricentis-sealights-product-training)

This portal is designed to accelerate your understanding of our solution, its core concepts, and the technologies that underpin your project. Inside the portal, you'll find:

* **Introduction modules** covering key terms, architecture, and workflows
* **Technical courses** tailored to the technologies used in your implementation (e.g., Java, .NET, and others)
* **Best practices and use cases** to guide you from day one

If you cannot access the portal, please contact your dedicated SeaLights CS Team (CSM, SA) or Support.
{% endhint %}

## Network Connectivity Validation <a href="#network-connectivity-validation" id="network-connectivity-validation"></a>

To ensure a smooth onboarding experience, we kindly request that your team completes a **network connectivity check** before any onboarding activity. This check confirms that SeaLights agents will be able to communicate securely with their respective servers. Please coordinate with your **IT or network security team** in advance, as firewall adjustments may require internal approvals or lead time. Verifying connectivity ahead of time helps prevent delays later in the onboarding process.

**What needs to be done:**

* Run a simple connectivity test from **each relevant machine**, including:
  * Local developer machines (if applicable)
  * CI/CD infrastructure (GitHub Actions, GitLab CI, ADO, Jenkins…)
  * Application servers or containers (Testing environments)
  * Test Automation machines
* Confirm that these systems can reach our servers and return a successful response for the following Key Endpoints:
  * **Required**: `https://<your-custom-domain>.sealights.co`
  * **Optional but recommended**: `https://agents.sealights.co`
* If a proxy is in use, ensure it allows outbound connections to the above domains over port **443 (TLS v1.2/1.3)**.
* For teams who have not yet received their dedicated account domain, use: `https://connect.sealights.co`

For exact command-line instructions and troubleshooting steps, please refer to our connectivity documentation: [agents-connectivity](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/general/agents-connectivity "mention")