Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Overview

Installation

Jenkins: SeaLights Jenkins plugin - Installation and setup

Java: Downloading the java agent files

Node.js: Downloading the Node.js agent file

Initiate Build

Jenkins: SeaLights Jenkins plugin - Generating a session ID

Java: Using Java Agents - Generating a session ID

Node.js: Using Node.js Agent - Generating a session ID

Scan Binaries & Scripts

Jenkins + Maven: SeaLights Jenkins plugin - Scanning Builds and running Unit Tests using Maven

Gradle: Scanning Builds and Tests using Gradle plugin

Java: Using Java Agents - Scanning a build

Node.js: Using Node.js Agents - Scanning a build

Javascript for UI: SeaLights Node.js agent - Running Front-end Tests

Capturing coverage & Test information - Unit Tests

Jenkins + Maven: SeaLights Jenkins plugin - Scanning Builds and running Unit Tests using Maven

Gradle: Scanning Builds and Tests using Gradle plugin

Java: Using Java Agents - Installing Test Listener as Java Agent + Using Java Agents - Running Tests

Node.js using Mocha: Running Tests using Mocha test framework

Node.js using TAP: Running Tests using TAP test framework

Node.js: Using Node.js Agents - Running backend server using SeaLights agent + Using Node.js Agent - Running Tests

Capture coverage - Functional Tests

Java: SeaLights Jenkins Plugin - Installing Test Listener as Java Agent

Node.js: Using Node.js Agents - Running backend server using SeaLights agent

Javascript for UI: This is done through the instrumented javascript files deployed to the server

Receive test results - Functional Tests

Jenkins + Maven: SeaLights Jenkins Plugin - Running tests using Maven

Jenkins: SeaLights Jenkins plugin - Running Tests using the SeaLights CLI

JMeter: Running test listener with JMeter

Java: Using Java Agents - Running Tests

Node.js: Using Node.js Agent - Running Tests


  • No labels