LogoLogo
Product
  • Knowledge Base
  • What's New
  • Guides
  • Welcome!
  • Intro to SeaLights
    • What is SeaLights
      • Glossary
      • Working in Conjunction with Your Quality / Coverage Tools
        • SeaLights vs SonarQube
        • SeaLights vs JaCoCo
    • Technical Overview
      • Test Stage Cycle
    • FAQ
  • User Story Coverage
    • Getting Started
    • User Story Challenges & Solution
      • Typical Implementation
      • The Challenges
      • The Solution
    • User Story Coverage Report Overview
      • Release Go / No Go Report
        • How to Generate / Edit the Report
      • User Story Quality Overview
        • How to Generate the User Story View
      • User Story Coverage Analysis
        • How to Generate the Analysis View
      • Uncovered Methods View
        • How to Generate the View
      • Customization
      • Integration
    • Use Cases by Persona
      • Managers
        • Informed Go/No Go Decisions Making
        • Effective Resources Prioritization
        • Overall Progress Monitoring
      • Developers
        • Code Quality Ownership
        • Seamless Collaboration with QA
        • Code Review Facilitator
      • QA Engineers
        • Test Execution Progress Monitoring
        • Testing Effort Prioritization
        • Testing Strategy Planing
    • Technical Overview
      • User Story Coverage Mechanism
      • Technical Architecture
      • Deployment Guide
        • US1_getResults.sh
        • US2_createReport.sh
        • US_UpdateConfluence.sh
  • Test Optimization
    • Getting Started
    • Test Execution Challenges & Solution
      • The Challenges
      • Test Optimization Solution
      • Test Optimization Main Advantages
    • Test Optimization Overview
      • Automated Test Optimization
      • Manual Test Optimization
      • Test Optimization for Pull Request
      • Test Selection Policies
        • Full Run Policy
        • No Code Changes Policy
        • Common Code Policy
        • Fastest Path to 100% Coverage Policy
      • Integrations
    • Use Cases by Persona
      • Managers
        • Fast Delivery
        • Resource Optimization
        • Thorough Testing in Tight Schedule
      • Developers
        • Exploring Only Relevant Test Failures
        • Faster Feedback Loop
        • Shift Left Testing
      • QA Engineers & Manual Testers
        • Faster & Focused Manual Testing
        • Optimizing Test Suite
        • Having Stable Product for Testing
    • Technical Overview
      • Test Optimization Mechanism
        • Associating Code With Tests
          • Statistical modeling
          • One-to-One Mapping
          • Calibration
        • Detecting Modified Code
        • Generating Test Recommendations
      • Technical Architecture
      • Deployment Guide
  • Quality Improvement
    • Getting Started
    • Challenges & Approach Comparison
      • The Challenges
      • Quality Improvement Approaches
      • Choosing the Right Approach
    • Quality Improvement Solution Overview
      • Test Gaps Analysis Report
        • How to Generate / Edit the Report
      • Coverage Trend Report
        • How to Generate / Edit the Report
      • Proof of Testing Report
        • How to Generate / Edit the Report
      • Release Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize Code Areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Threshold
        • STEP 5: Analyze Test Gaps
        • STEP 6: Write Tests
        • Step 7: Make a Go / No Go Decision Based on Quality Gate
        • STEP 8: Measure Defect Escape Rate
      • Over Time Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize code areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Goal
        • STEP 5: Set timeline
        • STEP 6: Write tests
        • STEP 7: Monitor progress
        • STEP 8: Measure Defect Escape Rate
    • Use Cases by Persona
      • Managers
        • Effective Prioritization & Budget Allocation
        • Tracking Progress & Measuring Impact
        • Data-Driven Release Decisions
        • Transparency & Communication
      • Developers
        • Mastering Code Coverage
        • Seamless Collaboration with QA
        • Code Quality Ownership
      • QA Engineers
        • Prioritizing Test Efforts
        • Contributing to Release Informed Decisions
        • Seamless Collaboration with Developers
        • Evaluating Testing Strategy
    • Technical Overview
      • Solution Mechanism
      • Technical Architecture
      • Deployment Guide
  • Features
    • Coverage Dashboard
    • Coverage Report
    • Test Gaps Report
      • Code Changes Calculation
        • Hidden Changes Detection
    • Test Optimization - Savings Breakdown
      • TIA Configuration
    • Settings
      • Token Access & Management
      • Quality Gates
Powered by GitBook
On this page
  • General
  • Coverage
  • Test Optimization
  • Security and Architecture

Was this helpful?

  1. Intro to SeaLights

FAQ

General

What is SeaLights?

SeaLights is a continuous quality optimization platform that empowers organizations to improve software quality by offering insights into test coverage across the entire development lifecycle. It goes beyond just providing coverage metrics, but also helps optimize testing efforts by recommending which tests to run based on code changes. This allows teams to focus their testing resources efficiently and deliver high-quality software faster.

How does SeaLights work?

SeaLights utilizes two lightweight agents: a Build Scanner and a Test Listener. The Build Scanner analyzes code changes to create an intelligent map of your codebase. The Test Listener tracks test execution and identifies which tests cover specific code areas. This data is then combined and analyzed to provide actionable insights, such as overall and modified code coverage, test gaps, and recommendations for test optimization.

How does SeaLights integrate with SonarQube?

While not directly integrating, SeaLights and SonarQube can work together seamlessly. SeaLights focuses on test optimization across various test types, while SonarQube focuses on static code analysis. They provide complementary insights, offering a holistic view of software quality. Read more: Working in Conjunction with Your Quality / Coverage Tools

Coverage

Why does SeaLights provide method-level coverage and not line-level coverage?

SeaLights focuses on method-level coverage because it offers a better representation of testable units and aligns with common testing practices. Line-level coverage can be misleading due to factors like dead code and comments.

SeaLights supports unit test coverage. Isn't it the same coverage as SonarQube or JaCoCo provide?

SeaLights offers broader coverage than just unit tests. It can analyze coverage across various types of tests, including integration, API, manual, and more, providing a more comprehensive picture of your testing strategy. Read More: Working in Conjunction with Your Quality / Coverage Tools

Test Optimization

How does SeaLights optimize testing?

SeaLights analyzes code changes and identifies which tests have been impacted by those changes. It then recommends skipping tests that haven't been affected, saving time and resources. This allows teams to focus their testing efforts on areas with the highest potential for introducing defects.

What are the benefits of test optimization?
  • Reduced Test Execution Time: By running only necessary tests, SeaLights can significantly decrease test execution time, allowing for faster feedback and release cycles.

  • Improved Resource Efficiency: By optimizing test runs, SeaLights reduces the hardware, software and manual resources required for testing, freeing up valuable resources for other tasks.

  • Increased Test Effectiveness: By focusing on tests relevant to code changes, SeaLights helps ensure that testing efforts are focused on the areas most likely to contain errors, leading to higher-quality software.

Security and Architecture

Does SeaLights access our source code?

No, SeaLights does not access your source code. It works by analyzing binary code and artifacts, uploading only metadata to its secure cloud platform. The listener running on-premise interacts with your CI and test environments only through secure uphold connections.

Do you support microservices and monolithic architectures?

Yes, SeaLights supports both microservices and monolithic architectures. It can track code changes and test execution across your entire application, including integration build groups that combine multiple microservices. SeaLights then maps this information and recommends tests based on the impacted areas.

PreviousTest Stage CycleNextGetting Started

Last updated 1 year ago

Was this helpful?