Does this skill automatically build my SDK changes?

Yes, the skill detects uncommitted changes in the packages directory and rebuilds the necessary tarballs before running tests to ensure your latest code is being validated.

What happens if I provide an incorrect test application name?

The skill will verify the application path; if it's not found, it will list all available test applications in the repository and ask you to select the correct one.

Which frameworks are supported by this E2E skill?

It supports any test application within the Sentry JavaScript repository, including Next.js, React, Node.js, Express, SvelteKit, Remix, and Nuxt.

Can I run tests for specific framework versions?

Absolutely. You can use the --variant flag (e.g., --variant nextjs-15) to target specific versions or configurations of a test application.

Sentry SDK E2E Tester

Name: Sentry SDK E2E Tester
Author: getsentry

bygetsentry

•

8,573

Security & Testing

Automates the end-to-end testing workflow for Sentry JavaScript SDK applications and packages.

About

The E2E skill streamlines the validation process for the Sentry JavaScript SDK by automating the complex sequence of rebuilding modified packages and running tests across various application environments. It intelligently detects changes in SDK packages, generates necessary tarballs, and executes E2E tests for specific applications like Next.js, Remix, or SvelteKit, ensuring that code changes maintain integrity across the entire Sentry ecosystem. This skill is essential for SDK contributors who need to verify their changes against real-world application scenarios without manually managing the build and test pipeline.

Key Features

Standardized reporting of test successes and failures
Automated validation of test application paths and availability
8,573 GitHub stars
Automatic detection and rebuilding of modified SDK packages
Support for application-specific test variants like Next.js 15
Integrated SDK tarball generation and management

Use Cases

Automatically rebuilding package tarballs after core SDK modifications
Verifying SDK changes across different framework integrations like Next.js or Remix
Running regression tests on specific environment variants before deployment

About

Key Features

Standardized reporting of test successes and failures
Automated validation of test application paths and availability
8,573 GitHub stars
Automatic detection and rebuilding of modified SDK packages
Support for application-specific test variants like Next.js 15
Integrated SDK tarball generation and management

Use Cases

Automatically rebuilding package tarballs after core SDK modifications
Verifying SDK changes across different framework integrations like Next.js or Remix
Running regression tests on specific environment variants before deployment