How to prepare for a Successful On-boarding (Standalone Environment)

The following key points describe the necessary prerequisites for onboarding an application to report Coverage & test metrics to Sealights from within a standalone, CI-independent setup. 

1. Configuring SeaLights in a Standalone Environment

This method is easier & takes less time to configure, but requires more manual input from the user throughout the onboarding process.

• Commands can either be run manually, or as part of an OS script
• SeaLights agents are invoked from the command line manually
• Relatively faster & less impact on performance of tested environment than a CI integration

2. Technical & Application layout

1. The following information is necessary to proceed with the onboarding process:
   1. Testing frameworks in use across all stages
   2. Build tool used, if applicable
   3. Application servers on which the onboarded app is deployed on
   4. Containers and their roles, if applicable
   5. Application specific package names/namespaces
   6. In case code is transpiled, ensure the existence and location of map files is known
   7. Specific Network/Security configuration (proxies, firewalls, etc), if applicable
2. Different technologies utilize different agents - verify your application's technology stack to determine which agents need to be used and in which components

3. Required Personnel & Permissions

1. Ensure the user has administrator permissions on the server(s) being worked on, as well as the deployed workspace
2. If your organization is working from behind a proxy - outbound HTTPS traffic must be allowed to reach the Sealights server
3. For the early stages of the POC, it is advisable that someone with knowledge about the application & technical layout be available in case any questions arise