Phased Onboarding - Welcome
If you became a SeaLights customer prior to January 2026, please discuss using this section with your SA or CSM — there are several assumptions in this document that may not apply to you.
Why a Phased Approach?
SeaLights recommends a phased onboarding approach. Each phase builds upon previous phases—gradually increasing the value you gain from SeaLights while adding configuration layers step by step.
This methodology lets you:
Start seeing value immediately — Get real-time coverage visibility in the first phase
Validate each step — Confirm everything works before moving forward
Minimize risk — Isolate issues to specific phases
Learn progressively — Build understanding as you go
In this section, each technology onboarding guide is structured into five distinct phases. These phases are designed to take users on a comprehensive onboarding journey tailored to each tech stack. By following these phases, users can gradually build their understanding and capabilities, starting with foundational concepts and moving towards more advanced configurations. This phased approach ensures a smooth transition, allowing users to integrate additional components with confidence and efficiency, while optimizing the learning curve for maximum retention and application.
What You'll Achieve In Each Phase
Phase 1
Core Coverage
Get visibility into your application's overall coverage, enabling you to assess testing completeness and improve release confidence.
Phase 2
Advanced Coverage Analytics
Gain a granular view of coverage across different test types (such as Integration, Regression, and E2E), enabling you to optimize your testing strategy and make more informed release decisions.
Phase 1
Phase 3
Continuous Coverage
Gain continuous, up-to-date visibility into build coverage by integrating SeaLights into your CI pipeline. Quickly understand how well new code changes are covered, enabling faster and more confident release decisions.
Phase 2
Phase 4
Test Impact Analysis
Accelerate delivery cycles by reducing test execution time without compromising quality confidence.
Phase 2
Phase 5
User Story Coverage Analytics
Get insights into the quality of individual user stories and their corresponding code changes across various testing stages.
Phase 3
Last updated
Was this helpful?

