uat-test-generator — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited uat-test-generator (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The UAT Test Case Generator skill provides specialized capabilities for generating User Acceptance Testing test cases from requirements and acceptance criteria. This skill enables systematic test case development, test data specification, traceability maintenance, and export to test management tools.
Generate UAT test cases from these acceptance criteria:
[Acceptance criteria in Given-When-Then format]
Include positive and negative scenarios.Create end-to-end test scenarios for:
[User story or feature description]
Generate complete user journey tests.Define test data requirements for these test cases:
[Test case list]
Include data setup, dependencies, and sample values.Calculate test coverage for:
Requirements: [Requirements list]
Test Cases: [Test case list]
Identify coverage gaps and missing tests.This skill integrates with the following business analysis processes:
Test Case ID: TC-XXX
Title: [Descriptive test title]
Requirement ID: REQ-XXX
Priority: High/Medium/Low
Preconditions:
- [Precondition 1]
- [Precondition 2]
Test Steps:
| Step | Action | Expected Result |
|------|--------|-----------------|
| 1 | [Action] | [Expected] |
| 2 | [Action] | [Expected] |
Test Data:
- [Data item 1]: [Value]
- [Data item 2]: [Value]
Postconditions:
- [State after test]| GWT Element | Test Case Element |
|---|---|
| Given | Preconditions |
| When | Test Steps (Actions) |
| Then | Expected Results |
| And | Additional steps or conditions |
| Type | Purpose | Examples |
|---|---|---|
| Positive | Verify correct behavior | Valid input, happy path |
| Negative | Verify error handling | Invalid input, edge cases |
| Boundary | Test limits | Min/max values, empty inputs |
| Integration | End-to-end flow | Complete user journeys |
| Regression | Verify unchanged behavior | Existing functionality |
Defect ID: DEF-XXX
Title: [Brief description]
Test Case: TC-XXX
Requirement: REQ-XXX
Severity: Critical/High/Medium/Low
Priority: P1/P2/P3/P4
Environment:
- Browser/Device: [Details]
- Environment: UAT/QA/Staging
Steps to Reproduce:
1. [Step 1]
2. [Step 2]
3. [Step 3]
Expected Result:
[What should happen]
Actual Result:
[What actually happened]
Attachments:
- [Screenshots, logs, etc.]| Metric | Formula | Target |
|---|---|---|
| Requirements Coverage | Tested Reqs / Total Reqs | 100% |
| Test Execution | Executed Tests / Total Tests | 100% |
| Pass Rate | Passed Tests / Executed Tests | 95%+ |
| Defect Detection | Defects Found / Total Defects | High |
| Priority | Criteria | Testing Approach |
|---|---|---|
| P1 - Critical | Core functionality, regulatory | Must test every release |
| P2 - High | Important features, frequent use | Test in full regression |
| P3 - Medium | Secondary features | Test in major releases |
| P4 - Low | Edge cases, rare scenarios | Test periodically |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.