rls-specimen-e2e

Execute Cypress and Nx end-to-end specimen accessioning tests locally.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/j-mckerracher/agent-research --skill rls-specimen-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rls-specimen-e2e
Source: https://github.com/j-mckerracher/agent-research/tree/main/skills-main/rls-specimen-e2e
Command: npx skills add https://github.com/j-mckerracher/agent-research --skill rls-specimen-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specimen accessioning end-to-end tests can be slow to set up and reproduce locally; this skill provides a concise, repeatable guide for executing Cypress and Nx-based E2E tests against the specimen accessioning app.

Core Features & Use Cases

  • Interactive Cypress UI runs for local debugging and exploration.
  • Headless CI-style executions for automated validation and dockerized environments.
  • Environment-targeted configurations to test against different dev servers and bases.

Quick Start

Open the Cypress Test Runner and run the rls-specimen-accessioning-e2e suite against the local dev server.

Frequently Asked Questions about rls-specimen-e2e

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

FAQPage Schema
How do I run Cypress E2E tests for specimen accessioning locally?

To run specimen accessioning E2E tests locally, open the Cypress Test Runner and execute the rls-specimen-accessioning-e2e suite against a running local dev server. The skill requires Cypress and Nx to be installed.

Can I run specimen accessioning E2E tests in a Docker environment?

Yes, you can execute headless CI-style E2E tests in Dockerized environments. The skill provides guidelines for Docker-based runs to automate validation against different deployment targets.

Do I need a running dev server to execute Nx E2E tests for specimen workflows?

Yes, a running dev server is required to execute the specimen accessioning E2E tests. You also need clear setup data, including valid credentials and test data, to validate the workflows properly.

How do I configure E2E tests to target different environment deployments?

Environment-specific configurations allow you to target different dev servers and base URLs. You can adjust these settings within the Cypress and Nx configuration to validate workflows against specific deployment targets.

Why are my specimen accessioning Cypress tests failing locally?

Failures often stem from an inactive dev server or missing setup data. Ensure your local server is running and that you have provided the required credentials and test data specified by the skill guidelines.