cells-test-creator

Generate and validate OpenWC and Sinon unit tests for Cells components.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-test-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cells-test-creator
Source: https://github.com/PixelDroid19/cells-agents/tree/main/skills/cells-test-creator
Command: npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-test-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Many Cells components lack deterministic, maintainable tests or contain tests coupled to internal implementation details, causing brittle failures and missed branch coverage; this Skill drives creation and validation of public-behavior unit tests to reach file-level 100% coverage and consistent repository conventions.

Core Features & Use Cases

  • Create or update mirrored test files under the test/ hierarchy that exercise only public behavior and emitted events.
  • Provide a base-test generator and a conventions validator to avoid private-member access, enforce OpenWC + Sinon patterns, and require sinon.restore in teardowns.
  • Coordinate a multi-agent loop: test creation, targeted test execution, lcov-based coverage auditing, and compliance validation to close branches and produce evidence.
  • Use cases: add missing tests for a component, increase file-level coverage to 100%, triage uncovered BRDA entries, and validate naming/structure and i18n considerations.

Quick Start

Generate a mirrored unit test for src/path/component.js using public behavior only and validate it until the target file reaches 100% file-level coverage.

Frequently Asked Questions about cells-test-creator

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

FAQPage Schema
How do I generate unit tests for OpenWC components to reach 100% file coverage?

To generate unit tests for OpenWC components with 100% file coverage, create mirrored test files under the test/ hierarchy that exercise only public behavior and emitted events. Validate naming conventions, avoid private-member access, and extract coverage data from build/coverage-reports/lcov.info to close uncovered branches.

Why do my Sinon unit tests fail when testing internal implementation details?

Sinon unit tests fail when coupled to internal implementation details because they cause brittle failures and miss branch coverage. To fix this, exercise only public behavior and emitted events, enforce OpenWC and Sinon patterns, and ensure sinon.restore is called in teardowns to maintain deterministic verification.

How do I triage uncovered BRDA entries in an lcov.info coverage report?

To triage uncovered BRDA entries in an lcov.info coverage report, run a targeted test execution workflow, audit the extracted lcov-based coverage data, and update your component tests to exercise the missed branches until file-level 100% coverage is achieved and validated.

Does this unit test generator work with BBVA Cells components?

Yes, this unit test generator is designed specifically for BBVA Cells components. It applies repo-local Cells-native test commands, uses OpenWC and Sinon patterns, and validates conventions to ensure deterministic public-behavior verification across your Cells architecture.

What is the best way to validate unit test conventions for OpenWC and Sinon?

The best way to validate unit test conventions for OpenWC and Sinon is to use a conventions validator that checks for private-member access, enforces mirrored test paths under test/, and requires sinon.restore in teardowns to ensure tests remain maintainable and deterministic.

Can I increase file-level coverage without accessing private members in my component tests?

You can increase file-level coverage without accessing private members by writing tests that exercise only public behavior and emitted events. This approach uses a generator and validator to produce compliant tests that avoid private-member access while still closing all uncovered branches.