e2e-test

Automate Playwright end-to-end tests for web application user journeys.

58|16|Updated May 14, 2026
One-click install
npx skills add https://github.com/NVIDIA-NeMo/nemo-platform --skill e2e-test-nvidia-nemo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/NVIDIA-NeMo/nemo-platform/tree/main/web/.agents/skills/e2e-test
Command: npx skills add https://github.com/NVIDIA-NeMo/nemo-platform --skill e2e-test-nvidia-nemo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of maintaining reliable end-to-end tests by providing a structured framework for user journey validation, reducing the time spent debugging flaky tests and manual verification.

Core Features & Use Cases

  • Page Object Model Integration: Encourages modular test design by encapsulating page interactions into reusable classes.
  • Robust Assertion Framework: Leverages Playwright's native auto-waiting and assertion capabilities to ensure test stability.
  • Use Case: Use this skill to define and execute a suite of tests that verify the critical path of a new feature in the Studio web UI, ensuring that user interactions like login, navigation, and data submission function correctly across different environments.

Quick Start

Use the e2e-test skill to run the full suite of Playwright tests for the current user flow and generate a trace report for any failures.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I automate end-to-end testing for web applications using Playwright?

End-to-end testing with Playwright is automated by defining user journey tests and utilizing page object models to encapsulate page interactions. The framework executes browser-based interactions and assertions to validate critical web UI paths.

What is the best way to structure Playwright tests to avoid flaky results?

To avoid flaky results in Playwright tests, structure tests using the Page Object Model integration to encapsulate interactions into reusable classes. This modular design leverages native auto-waiting capabilities to ensure robust test stability.

How do I debug failing Playwright user journey tests?

Debug failing Playwright user journey tests by generating and analyzing a trace report via the trace viewer. This failure analysis mechanism provides detailed execution logs to identify why browser-based interactions and assertions failed.

Does the e2e-test skill require a pre-configured Playwright environment?

Yes, the e2e-test skill requires a configured Playwright environment to perform browser-based interactions and assertions. You need this setup established before defining and executing user journey tests for your web applications.

Can I verify web UI login and navigation flows across different environments with Playwright?

Yes, you can verify web UI login, navigation, and data submission flows across different environments using Playwright. The skill facilitates executing user journey tests that ensure critical paths function correctly in various configurations.