General

• Application ready to integrate SeaLights with is identified

• Test stages that can be run against the application ready to integrate SeaLights with

• Relevant project members with proper permission set are identified and allocated

Network

• Connectivity validated to the SeaLights dashboard from every machine that our agent will be installed on and reporting from

  • Outbound connections to sealights.co domain on port 443 (TLS v1.2/1.3) are required via your firewall or a proxy

• Recommended command for validating connectivity is: curl -I https://<YourCustomerDomain>.sealights.co

  • Returned code must be HTTP Code OK (200)

  • If you don’t have yet a dedicated customer domain, you have the ability to use one of our generic URLs for validation curl -I https://app.sealights.co

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

  • SeaLights Jenkins plugin - Installation and setup - For Maven built by Jenkins Freestyle jobs

• 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

• Microsoft Visual C++ Redistributable for Visual Studio 2017 installed on any machine coverage will be captured on: https://www.visualstudio.com/downloads/

  • The 32bit version is: https://go.microsoft.com/fwlink/?LinkId=746571

  • The 64bit version is: https://go.microsoft.com/fwlink/?LinkId=746572

• Knowledge of architecture (32 or 64 bits) that the processes coverage will be captured from

• (If needed) Ability to download and run the Microsoft Process Explorer on machines that report coverage for debugging purposes.

  • See Official documentation page: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer