@tvlabs/wdio-service
v0.1.13
Published
WebdriverIO service that provides a better integration into TV Labs
Downloads
26,995
Maintainers
Readme
Introduction
The @tvlabs/wdio-service package uses a websocket to connect to the TV Labs platform before an Appium session begins, logging events relating to build upload and session creation as they occur. This offloads the responsibility of creating the TV Labs session from the POST /session Webdriver endpoint, leading to more reliable session requests and creation.
If a build path is provided, the service first makes a build upload request to the TV Labs platform, and then sets the tvlabs:build capability to the newly created build ID.
The service then makes a session request and then subscribes to events for that request. Once the session has been filled and is ready for the Webdriver script to begin, the service receives a ready event with the TV Labs session ID. This session ID is injected into the capabilities as tvlabs:session_id on the Webdriver session create request.
Additionally, the service automatically injects an Authorization header with your API key (formatted as Bearer ${apiKey}) into all requests to the TV Labs platform. If you have already set an Authorization header in your configuration, the service will respect your existing header and not override it.
The service also adds a unique request ID for each request made. The service will generate and attach an x-request-id header before each request to the TV Labs platform. This can be used to correlate requests in the client side logs to the Appium server logs.
Installation
In your WebdriverIO project, run one of the following commands to install:
NPM
npm i --save @tvlabs/wdio-serviceYarn
yarn add @tvlabs/wdio-serviceUsage
WebdriverIO Test Runner
To use this as a WebdriverIO test runner service, include the service in your WebdriverIO configuration file (e.g. wdio.conf.ts) with your TV Labs API key set in the options.
import { TVLabsService } from '@tvlabs/wdio-service';
export const config = {
// ...
services: [[TVLabsService, { apiKey: process.env.TVLABS_API_KEY }]],
// ...
};Standalone (remote)
To use this with WebdriverIO remote but without the test runner, call beforeSession() before instantiating the remote.
import { remote } from 'webdriverio';
import { TVLabsService } from '@tvlabs/wdio-service';
async function run() {
const capabilities = { ... };
const wdOpts = {
capabilities,
hostname: 'appium.tvlabs.ai',
port: 4723
};
// NOTE: wdOpts must be the same reference passed to remote()
const service = new TVLabsService(
{ apiKey: process.env.TVLABS_API_KEY },
capabilities,
wdOpts,
);
await service.beforeSession(wdOpts, capabilities, [], '');
const driver = await remote(wdOpts);
try {
// ...
} finally {
await driver.deleteSession();
}
}
run();Attaching to an Existing Session
WebdriverIO's attach() binds a driver to a session that was created earlier — possibly by a different process. Use TVLabsService.fromSession() alongside attach() to keep TV Labs telemetry (lastRequestId(), requestMetadata(), sessionMetadata()) working for the attaching driver, without recreating the session.
The portable handle is the Appium session ID — the value of driver.sessionId after the original remote() call. Pass it through whatever channel fits your setup (env var, fixture, queue message, file).
Creating the session
import { remote } from 'webdriverio';
import { TVLabsService } from '@tvlabs/wdio-service';
const capabilities = { ... };
const wdOpts = {
capabilities,
hostname: 'appium.tvlabs.ai',
port: 4723,
};
const service = new TVLabsService(
{ apiKey: process.env.TVLABS_API_KEY },
capabilities,
wdOpts,
);
await service.beforeSession(wdOpts, capabilities, [], '');
const driver = await remote(wdOpts);
// Hand off driver.sessionId to wherever the attaching process will pick it up
const appiumSessionId = driver.sessionId;Attaching to the session
import { attach } from 'webdriverio';
import { TVLabsService } from '@tvlabs/wdio-service';
const wdOpts = {
capabilities: {},
hostname: 'appium.tvlabs.ai',
port: 4723,
};
// appiumSessionId received from the session-creating process
const service = TVLabsService.fromSession(
appiumSessionId,
{ apiKey: process.env.TVLABS_API_KEY },
wdOpts,
);
const driver = await attach({
sessionId: appiumSessionId,
...wdOpts,
options: wdOpts,
});
try {
const element = await driver.$('#my-button');
await element.click();
const requestId = service.lastRequestId();
const metadata = await service.requestMetadata(appiumSessionId, requestId);
const session = await service.sessionMetadata(appiumSessionId);
} finally {
await service.disconnect();
// Only delete the session if this process owns its lifecycle.
}Note:
lastRequestId()is per-instance — eachTVLabsServicetracks request IDs that flow through its owntransformRequesthook. UserequestMetadata()andsessionMetadata()(both keyed by Appium session ID) for telemetry that needs to span instances.
Options
apiKey
- Type:
string - Required: Yes
- Description: TV Labs API key used for authentication to the platform
buildPath
- Type:
string - Required: No
- Description: Path to the packaged build to use for the session. When provided, this will perform a build upload before the session is created, and sets the
tvlabs:buildcapability to the newly created build ID. The build is uploaded under the organizations default App unless theappoption is provided
app
- Type:
string - Required: No
- Description: The slug of the app on the TV Labs platform to use to upload the build. When not provided, the organization's default app is used. You may find or create an app on the Apps page in the TV Labs platform.
retries
- Type:
number - Required: No
- Default:
3 - Description: Maximum number of attempts to create a session before failing
reconnectRetries
- Type:
number - Required: No
- Default:
5 - Description: Maximum number of attempts to re-connect if the connection to TV Labs is lost.
attachRequestId
- Type:
boolean - Required: No
- Default:
true - Description: Controls whether or not to attach an
x-request-idheader to each request made to the TV Labs platform.
continueOnError
- Type:
boolean - Required: No
- Default:
false - Description: Whether to continue the session request if any step fails. When
true, the session request will still be made with the original provided capabilities. Whenfalse, the service will exit with a non-zero code.
Methods
lastRequestId()
- Returns:
string | undefined - Description: Returns the last request ID attached to a request made to the TV Labs platform. Useful for correlating client-side logs with server-side logs. Returns
undefinedif no request has been made yet or ifattachRequestIdisfalse.
requestMetadata()
- Parameters:
appiumSessionId: string, requestIds: string | string[] - Returns:
Promise<TVLabsRequestMetadata | TVLabsRequestMetadataResponse> - Description: Fetches metadata for one or more request IDs from the TV Labs platform. Pass a single request ID to get its metadata directly; pass an array to get a map keyed by request ID.
Note: Request metadata is processed asynchronously on the TV Labs platform. Fetch after the session ends, or wait a few seconds after the request, to ensure the data is available.
Example
import { remote } from 'webdriverio';
import { TVLabsService } from '@tvlabs/wdio-service';
const capabilities = { ... };
const wdOpts = { ... };
const service = new TVLabsService(
{ apiKey: process.env.TVLABS_API_KEY },
capabilities,
wdOpts,
);
await service.beforeSession(wdOpts, capabilities, [], '');
const driver = await remote(wdOpts);
let requestId;
try {
const element = await driver.$('#my-button');
await element.click();
requestId = service.lastRequestId();
} finally {
await driver.deleteSession();
}
// Single request
if (requestId) {
const metadata = await service.requestMetadata(driver.sessionId, requestId);
console.log('Request metadata:', metadata);
}
// Multiple requests
const multiMetadata = await service.requestMetadata(driver.sessionId, [
'request-id-123',
'request-id-456',
'request-id-789',
]);
console.log('Multiple requests metadata:', multiMetadata);sessionMetadata()
- Parameters:
appiumSessionId: string - Returns:
Promise<TVLabsSessionMetadataResponse> - Description: Fetches metadata for a session by Appium session ID from the TV Labs platform.
Note: Partial metadata will be available immediately after session creation. Fields such as recording end time, session end time, and session duration are populated asynchronously after the session ends — they will be
nulluntil then.
Tip: The response includes both IDs —
data.idis the TV Labs session ID (useful for deep-linking intohttps://tvlabs.ai/app/sessions/:id) anddata.appium.session_idis the Appium session ID. Consumers that only have the Appium session ID can resolve the TV Labs session ID from this response.
Example
import { remote } from 'webdriverio';
import { TVLabsService } from '@tvlabs/wdio-service';
const capabilities = { ... };
const wdOpts = { ... };
const service = new TVLabsService(
{ apiKey: process.env.TVLABS_API_KEY },
capabilities,
wdOpts,
);
await service.beforeSession(wdOpts, capabilities, [], '');
const driver = await remote(wdOpts);
const { sessionId } = driver;
try {
// ...
} finally {
await driver.deleteSession();
}
const sessionMetadata = await service.sessionMetadata(sessionId);
const { data: {
device: {
make: { display_name: make },
model: { display_name: model, year },
},
recording: { start_time },
} } = sessionMetadata;
console.log(`Recording on ${year} ${make} ${model} started at ${start_time}`);disconnect()
- Returns:
Promise<void> - Description: Closes any long-lived connections held by the service (currently the metadata channel WebSocket opened by
requestMetadata()). Call this when you are finished with the service so the process can exit. Safe to call when no channel was opened, and safe to call multiple times.
Note: Await all in-flight
requestMetadata()calls before callingdisconnect(). Tearing down the metadata channel while a request is pending will cause that call to reject.
Static Factory
TVLabsService.fromSession()
- Parameters:
appiumSessionId: string, options: TVLabsServiceOptions, wdOpts: Options.WebdriverIO - Returns:
TVLabsService - Description: Creates a
TVLabsServiceinstance bound to an existing Appium session without callingbeforeSession(). Use this when you have an Appium session ID (the value ofdriver.sessionIdafter a previousremote()call) and want to attach to that session via WebdriverIO'sattach().
The factory:
- Injects the
Authorizationheader onwdOpts. - Installs the
x-request-idtracking hook onwdOpts(unlessattachRequestId: false), solastRequestId()works on the attached driver. - Records the Appium session ID for use by
appiumSessionId,requestMetadata(), andsessionMetadata().
Important:
wdOptsmust be the same reference later passed toattach().
Note: Calling
beforeSession()on a service created viafromSession()throws aSevereServiceErrorto prevent accidentally creating a duplicate session.
Tip: To verify the session exists before using it, call
await service.sessionMetadata(appiumSessionId)immediately after construction. It throws if the session is not found or the API key cannot access it.
appiumSessionId
- Type: getter
- Returns:
string | undefined - Description: Returns the Appium session ID bound via
fromSession(), orundefinedfor service instances created through the standard constructor.
