npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

wdio-test-ledger-service

v9.2.11

Published

WebdriverIO server to send reporter data to testledger.dev

Readme

WebdriverIO Test Ledger Service

WDIO service that takes results from wdio-test-ledger-reporter and uploads them to testledger.dev

testledger.dev stores and tracks all test runs with extensive details about each test. This gives you a historical overivew of how your tests are running.

Setup is very simple. All you need to do is add the service and reporter to the services and reporters arrays in your wdio.conf.js file.

Install the service

npm install wdio-test-ledger-service

Add the service to the services array in wdio.conf.js

services: [['test-ledger', {
	reporterOutputDir : './testledger',            // This must match the outputDir from the wdio-test-reporter
	apiUrl            : 'app-api.testledger.dev',  // Defaults to app-api.testledger.dev if none is set
	apiToken          : 'tl_abc123_yoursecret',    // API token from app.testledger.dev
	projectId         : 123,                       // Only needed if using more than one project
	appVersion        : '2.8.10',                  // The code version can also be set here
	enableFlaky       : 1,                         // Will mark tests as flaky if it detects them based on previous runs
	uploadArtifacts   : true,                      // Enable screenshot/video artifact uploads
	screenshotDir     : './screenshots',           // Directory containing screenshots
	videoDir          : './_results_/videos',      // Directory containing videos (e.g. from wdio-video-reporter)
}]],

You can create an API token in the UI under Settings -> Profile -> API Keys.

Tip: Use the TESTLEDGER_API_TOKEN environment variable instead of hardcoding the token:

services: [['test-ledger', {
	reporterOutputDir : './testledger',
	projectId         : 123,
}]],
export TESTLEDGER_API_TOKEN="tl_abc123_yoursecret"
npx wdio run wdio.conf.js

Add the wdio-test-ledger-reporter to the reporters array in wdio.conf.js

npm install wdio-test-ledger-reporter
reporters : [[`test-ledger`, {
	outputDir : `./testledger`
}]]

Artifact Uploads (Screenshots & Videos)

The service can upload screenshots and videos to Test Ledger, making them viewable directly in the UI alongside test results.

Configuration

| Option | Type | Description | |--------|------|-------------| | uploadArtifacts | boolean | Enable artifact uploads. Default: false | | screenshotDir | string | Directory containing screenshot files (png, jpg, jpeg, gif, webp) | | videoDir | string | Directory containing video files (webm, mp4, mov) |

Example with wdio-video-reporter

reporters: [
	['video', {
		saveAllVideos : false,       // Only save videos for failed tests
		videoSlowdownMultiplier : 3,
		outputDir : './_results_/videos'
	}],
	['test-ledger', {
		outputDir : './testledger'
	}]
],
services: [['test-ledger', {
	reporterOutputDir : './testledger',
	apiToken          : 'tl_abc123_yoursecret',  // Or use TESTLEDGER_API_TOKEN env var
	uploadArtifacts   : true,
	screenshotDir     : './screenshots',
	videoDir          : './_results_/videos'
}]]

Artifacts are matched to test suites based on filename. The service looks for the spec file name within the artifact filename.

Environment variables

Environment variables can be set when running tests:

  • TESTLEDGER_API_TOKEN - API token for authentication (recommended for CI)
  • RUN_TITLE - Title of the test run. This might be something like a Jira issue key. Defaults to a timestamp if not specified
  • RUN_UUID - UUID which can be used to directly link to the test run results. e.g. https://app.testledger.dev/runs/
  • APP_VERSION - Set the version of app this test run ran against