sdlc-uat-tests

Runs product-level acceptance testing across all features before PR creation in the Agentic SDLC workflow.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-uat-tests-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-uat-tests
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/sdlc-uat-tests
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-uat-tests-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Individual feature tests can pass while the integrated product still fails real user journeys. This Skill validates the whole product against all requirements and acceptance criteria in a confirmed safe live environment before any pull request is created. ## Core Features & Use Cases - Whole-Product UAT Matrix: Builds a UAT matrix from all requirements and acceptance criteria, covering cross-feature user journeys and negative criteria. - Harness-Aware GUI Testing: Routes GUI journeys through the exact declared harness (computer-use, browser, or Playwright) with fresh accessibility state per action and an ordered action ledger. - Independent Evidence Oracles: Requires API, database, or service oracles for data-backed GUI flows, and writes a structured UAT report to evidence/uat/uat-report.md. - Use Case: After all feature commits are complete in an Agentic SDLC run, the coordinator invokes this Skill to execute end-to-end acceptance testing, classify failures (EVALUATION_DEFECT, DESIGN_DEFECT, SPEC_GAP, ENVIRONMENT_DEFECT), and gate PR creation on a passing result. ## Quick Start Ask the Agentic SDLC coordinator to run UAT validation on the current branch after all feature commits are complete, using the confirmed live experiment environment defined in docs/requirements.md.

Frequently Asked Questions about sdlc-uat-tests

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

FAQPage Schema
How do I run user acceptance testing before creating a pull request?

Run UAT after all feature commits are complete by building a test matrix from acceptance criteria, executing end-to-end user journeys in a confirmed safe environment, and recording evidence in a UAT report. PR creation is gated on all P0 criteria passing.

What is the difference between UAT and single-feature evaluation?

UAT validates the full integrated product including cross-feature journeys and negative criteria, while single-feature evaluation checks one feature in isolation. Use a dedicated evaluation skill for individual features and UAT only when all feature commits are complete.

Can browser or Playwright tests replace computer-use GUI testing?

No. When a UAT matrix row declares computer-use, the GUI journey must run through that exact harness with the declared browser. Browser or Playwright evidence cannot substitute, and fresh accessibility state must be captured after each action.

When should a live experiment environment not be used for testing?

Never use production or unconfirmed environments. The environment must be explicitly marked provided, confirmed as non-production or disposable, and the actions must fit the recorded allowed operations. Otherwise classify the blocker instead of improvising.

Why are screenshots alone insufficient as UAT pass evidence?

Screenshots only show visual state, not underlying data correctness. For data-backed GUI journeys, an independent API, database, or service oracle must corroborate the observed behavior before a flow can be marked as passed.