openelis-test-catalog-qa

Automate browser-based QA testing for OpenELIS Global with Playwright and generate pass/fail reports.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/DIGI-UW/OpenELIS-QA --skill openelis-test-catalog-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openelis-test-catalog-qa
Source: https://github.com/DIGI-UW/OpenELIS-QA/tree/main
Command: npx skills add https://github.com/DIGI-UW/OpenELIS-QA --skill openelis-test-catalog-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenELIS QA teams spend significant effort validating end-to-end workflows across the platform. This skill provides a repeatable, scripted approach to exercise OpenELIS modules, capture results, and report findings, reducing manual toil and increasing traceability.

Core Features & Use Cases

  • Automates browser-based QA across OpenELIS modules (Reports, Validation, Dashboard, Admin, and more) using Playwright-driven tests and accompanying manual documentation.
  • Produces structured pass/fail reports and logs with screenshots, enabling rapid triage and reproducibility.
  • Generates Jira tickets for failures to integrate with existing defect tracking and release processes.

Quick Start

Run automated gap suites to validate the OpenELIS QA surface and bootstrap regression testing in your environment.

Frequently Asked Questions about openelis-test-catalog-qa

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

FAQPage Schema
How do I automate regression testing for OpenELIS Global modules?

Automated regression testing for OpenELIS Global is handled by driving a Playwright browser to execute end-to-end test suites across modules like Reports, Validation, and Admin. This produces structured pass/fail reports and screenshots for triage.

Can I automatically create Jira tickets for OpenELIS QA test failures?

Yes, Jira ticket creation for failures is integrated directly into the automated QA flow. When a test fails, the system generates a Jira ticket to integrate with existing defect tracking and release processes.

Does OpenELIS automated QA handle CSRF tokens and authentication flows?

The automated QA process implements a safe, CSRF-aware flow to interact with OpenELIS Global. This handles authentication requirements correctly while executing test suites with granular logging and error handling.

What's the best way to validate end-to-end workflows across OpenELIS Global?

Validating end-to-end workflows across OpenELIS is best done using a scripted approach that exercises modules like Dashboard and Admin. It captures results and generates reports with screenshots, reducing manual toil and increasing traceability.

How do I get structured pass/fail reports from OpenELIS automated tests?

Structured pass/fail reports are generated automatically by executing automated gap suites against OpenELIS. The reports include granular logs and screenshots to enable rapid triage and reproducibility of test results.

Do I need Playwright to run automated QA tests on OpenELIS Global?

Playwright is used as the underlying browser driver to execute automated QA tests on OpenELIS Global. It powers the interaction with end-to-end workflows across tests, validation, reports, and admin areas.