Onboarding Pre-Requisites
General
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
Item | Description | Relevant Approach(es) |
|---|---|---|
Testing frameworks | Frameworks used across all test stages (e.g., JUnit, NUnit, Pytest) | All |
Build tool | Build system used (e.g., Maven, Gradle, MSBuild), if applicable | All |
Application servers | Runtime environments (e.g., Tomcat, IIS) | All |
Containers | Containers (e.g., Docker, Kubernetes) and their purpose | All |
Package names/namespaces | Application-specific packages or namespaces for mapping coverage | All |
Map files (if transpiled) | Location of source maps (e.g., from TypeScript, Babel) | All |
Network/security configuration | Proxy/firewall details: allow outbound HTTPS access to SeaLights | All |
Source Control System (SCM) | e.g., GitHub, Bitbucket, GitLab | All |
Build & test trigger type | CI-only: auto/manual triggers or job chaining | CI/CD only |
Runtime arguments | App runtime options or parameters | All |
Agent compatibility | Match SeaLights agent types to tech stack (Java, .NET, etc.) | All |
Deployment Script / Runtime System Access | For CD/Standalone: ability to run the agent where the app is deployed | CD-only & Standalone |
Agents compatibility
Java
Ability to download one or more of the following, according to the setup:
SeaLights Java agent from Downloading the java agent files
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
Npm & Node installed on any machine that will be running the sealights agent: Downloading the Node.js agent file
Sealights node agent installed on any machine that will be running the sealights agent: Downloading the Node.js agent file
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
Dotnet
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
TBC
Golang
TBC