writing-e2e-tests

Create and run Playwright end-to-end tests for Opik features and pages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jimmy071919/iiii-project --skill writing-e2e-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-e2e-tests
Source: https://github.com/jimmy071919/iiii-project/tree/main/opik/.agents/skills/writing-e2e-tests
Command: npx skills add https://github.com/jimmy071919/iiii-project --skill writing-e2e-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating and running end-to-end tests for Opik features, pages, or branches, ensuring functionality and UI integrity without manual testing.

Core Features & Use Cases

  • Automated Test Creation: Generates end-to-end tests based on user-defined features, pages, or branches.
  • Test Execution: Runs the tests locally to verify functionality and UI.
  • Use Case: When developing a new feature, use this Skill to create a test that will automatically verify the feature's functionality and UI, saving time and reducing the likelihood of bugs.

Quick Start

Run the writing-e2e-tests skill to add an E2E test for the feature I just built.

Frequently Asked Questions about writing-e2e-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end tests for Opik features?

Automate end-to-end tests for Opik features by generating test scripts that utilize Playwright for UI interaction and Python SDK for data seeding. This ensures functionality and UI integrity without requiring manual testing processes.

Can I use Playwright and Python SDK together for UI automation?

Yes, Playwright and Python SDK are used together for UI automation, with Playwright handling UI interactions and Python SDK managing data seeding to comprehensively verify functionality and UI integrity in Opik applications.

What is the best way to verify UI integrity when developing new Opik features?

The best way to verify UI integrity is to generate and execute automated end-to-end tests locally. This automatically verifies newly developed features and pages, saving time and reducing the likelihood of bugs.

Do I need to manually write test scripts to verify Opik branches?

No, you do not need to manually write test scripts to verify Opik branches. The process automates the creation of end-to-end tests based on user-defined features, pages, or branches to run locally.

Why use automated end-to-end testing instead of manual checks for Opik pages?

Automated end-to-end testing ensures consistent functionality and UI integrity for Opik pages while saving time. It automatically verifies features during development, significantly reducing the likelihood of bugs compared to manual checks.

How to start running E2E tests for a newly built Opik feature?

To start running E2E tests, trigger the writing-e2e-tests skill to add a test for the feature you just built. It will automatically generate and execute the necessary Playwright and Python SDK tests locally.