test-writer

Write and modify NUnit test classes for Decentraland Explorer UI automation.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/decentraland/explorer-automation --skill test-writer-decentraland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-writer
Source: https://github.com/decentraland/explorer-automation/tree/main/.claude/skills/test-writer
Command: npx skills add https://github.com/decentraland/explorer-automation --skill test-writer-decentraland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone effort of writing and updating UI automation tests by giving you a consistent way to create NUnit test classes that validate Decentraland Explorer behavior through the Page Object Model.

Core Features & Use Cases

  • Writes and updates NUnit test classes for the Explorer UI automation suite under Tests/Tests/, including new fixtures and additional test methods.
  • Ensures correct test orchestration by structuring tests around the expected workflow (Navigate → Verify → Interact → Clean up) and relying on view methods instead of raw locators.
  • Guides safe test hygiene and reliability by following BaseTest lifecycle conventions (Escape cleanup, screenshot on failure) and enforcing independent tests with proper panel closing.

Quick Start

Write a new Explorer test class that opens a specified panel, waits for the expected element state, performs the user flow needed for your scenario, and closes the panel before finishing.

Frequently Asked Questions about test-writer

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

FAQPage Schema
How do I write NUnit test classes for Decentraland Explorer UI automation?

To write NUnit test classes for Decentraland Explorer UI automation, target the Tests/Tests/ directory and implement scenarios using the Page Object Model via Views, structuring test methods around the Navigate→Verify→Interact→Clean up workflow.

What is the correct test pattern for Explorer UI integration testing?

The correct pattern for Explorer UI integration testing is Navigate→Verify→Interact→Clean up, relying on view methods with element-based waits instead of raw locators, and ensuring proper panel closing for independent test hygiene.

How do I add a new test method to an existing NUnit Explorer test fixture?

Adding a new test method to an existing NUnit Explorer test fixture requires following the BaseTest lifecycle conventions, using view methods for interactions, and executing Escape cleanup to safely close panels before the test finishes.

Why does my Explorer UI test fail during panel navigation and interaction?

Explorer UI tests fail during panel navigation when using raw locators instead of view methods or missing element-based waits, requiring strict adherence to the Navigate→Verify→Interact→Clean up pattern and BaseTest screenshot-on-failure conventions for reliability.

Can I use raw locators when writing NUnit tests for the Explorer?

No, Explorer-specific rules prohibit raw locators when writing NUnit tests, requiring all element interactions and state verifications to route through Page Object Model view methods to ensure reliable UI automation.

Does test-writer support Allure reporting for NUnit Explorer UI tests?

Test-writer focuses on generating NUnit test classes for Explorer UI automation with the Page Object Model, and while Allure reporting is part of the testing context, the core task centers on fixture creation and test orchestration rather than report generation.