# Onboarding Pre-Requisites

## General <a href="#general" id="general"></a>

* The application to integrate with SeaLights is identified and ready.
* Test stages that can be run against the application are ready to integrate SeaLights with
* Relevant project members with proper permission set are identified and allocated

## Technical and Application Checklist <a href="#technical-and-application-checklist" id="technical-and-application-checklist"></a>

<table data-header-hidden><thead><tr><th width="216.69921875">Item</th><th width="360.1171875">Description</th><th>Relevant Approach(es)</th></tr></thead><tbody><tr><td>Testing frameworks</td><td>Frameworks used across all test stages (e.g., JUnit, NUnit, Pytest)</td><td>All</td></tr><tr><td>Build tool</td><td>Build system used (e.g., Maven, Gradle, MSBuild), if applicable</td><td>All</td></tr><tr><td>Application servers</td><td>Runtime environments (e.g., Tomcat, IIS)</td><td>All</td></tr><tr><td>Containers</td><td>Containers (e.g., Docker, Kubernetes) and their purpose</td><td>All</td></tr><tr><td>Package names/namespaces</td><td>Application-specific packages or namespaces for mapping coverage</td><td>All</td></tr><tr><td>Map files (if transpiled)</td><td>Location of source maps (e.g., from TypeScript, Babel)</td><td>All</td></tr><tr><td>Network/security configuration</td><td>Proxy/firewall details: allow outbound HTTPS access to SeaLights</td><td>All</td></tr><tr><td>Source Control System (SCM)</td><td>e.g., GitHub, Bitbucket, GitLab</td><td>All</td></tr><tr><td>Build &#x26; test trigger type</td><td>CI-only: auto/manual triggers or job chaining</td><td>CI/CD only</td></tr><tr><td>Runtime arguments</td><td>App runtime options or parameters</td><td>All</td></tr><tr><td>Agent compatibility</td><td>Match SeaLights agent types to tech stack (Java, .NET, etc.)</td><td>All</td></tr><tr><td>Deployment Script / Runtime System Access</td><td>For CD/Standalone: ability to run the agent where the app is deployed</td><td>CD-only &#x26; Standalone</td></tr></tbody></table>

## Agents compatibility  <a href="#agents-compatibility" id="agents-compatibility"></a>

### Java <a href="#java" id="java"></a>

* Ability to download one or more of the following, according to the setup:
  * SeaLights Java agent from [downloading-the-java-agent](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/java-agent/default-usage-cli/downloading-the-java-agent "mention")
  * SeaLights Maven plugin from Maven Central or local Maven repo
  * SeaLights Gradle plugin from Maven Central or local Maven repo
* Knowledge and ability to configure the JVM arguments of the application servers

### NodeJS and Client-Side JS <a href="#nodejs-and-client-side-js" id="nodejs-and-client-side-js"></a>

* Npm & Node installed on any machine that will be running the sealights agent: [downloading-the-node.js-agent](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/node.js-agent/downloading-the-node.js-agent "mention")
* Sealights node agent installed on any machine that will be running the sealights agent: [downloading-the-node.js-agent](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/node.js-agent/downloading-the-node.js-agent "mention")
* For unit tests coverage - The ability to generate the `coverage-final.json` (NYC JSON coverage report)
* For Client-Side JS, Ability to generate Source maps of ‘original source’ quality: [javascript-and-node.js-source-map-files](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/node.js-agent/javascript-and-node.js-source-map-files "mention")

### .Net <a href="#dotnet" id="dotnet"></a>

* Knowledge of architecture (32 or 64 bits) that which the process coverage will be captured
* (If needed) Ability to download and run the Microsoft Process Explorer on machines that report coverage for debugging purposes.
  * See the Official documentation page: <https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer>

### Python <a href="#python" id="python"></a>

TBC

### Golang <a href="#golang" id="golang"></a>

TBC

### ABAP <a href="#golang" id="golang"></a>

TBC