Compare commits
5
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
8e6547659c | ||
|
|
794881e18b | ||
|
|
ac6f696f19 | ||
|
|
84225828bd | ||
|
|
e8ddf82040 |
@@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
name: corp-v1-channel-uat
|
name: corp-v1-channel-uat
|
||||||
description: Use when validating a deployed Corp v1 environment through UAT journeys.
|
description: Use when validating a deployed Corp v1 environment through UAT journeys.
|
||||||
version: 1.1.3
|
version: 1.3.0
|
||||||
author: Hermes Agent
|
author: Hermes Agent
|
||||||
license: MIT
|
license: MIT
|
||||||
metadata:
|
metadata:
|
||||||
@@ -42,13 +42,14 @@ If any identity is mutable, missing, or contradictory, record `BLOCKED` rather t
|
|||||||
|
|
||||||
## Responsibilities
|
## Responsibilities
|
||||||
|
|
||||||
1. Maintain a dedicated pnpm E2E repository with versioned journeys.
|
1. Maintain a dedicated pnpm E2E repository as the authoritative home for functional non-unit tests and their fixtures, configuration, runner, and evidence contract.
|
||||||
2. Execute journeys against the exact deployed environment supplied by Delivery.
|
2. Keep application image/container/Helm build, rendering, publication, and static artifact validation in Delivery. The E2E repository must not build/publish application images, install Helm, render charts, or validate artifact publication.
|
||||||
3. Collect machine-readable and human-reviewable evidence.
|
3. Execute source-coupled functional non-unit suites against an exact application-source checkout and black-box journeys against the exact deployed environment supplied by Delivery.
|
||||||
4. Distinguish product failures, environment failures, and test defects.
|
4. Collect machine-readable and human-reviewable evidence.
|
||||||
5. Return product/environment failures to Kanban and Delivery with reproducible evidence.
|
5. Distinguish product failures, environment failures, and test defects.
|
||||||
6. Rerun the affected journey set after a verified redeployment.
|
6. Return product/environment failures to Kanban and Delivery with reproducible evidence.
|
||||||
7. Hand a `UAT_PASSED` or `UAT_FAILED` verdict to Releases without implying release approval.
|
7. Rerun the affected journey set after a verified redeployment.
|
||||||
|
8. Hand a `UAT_PASSED` or `UAT_FAILED` verdict to Releases without implying release approval.
|
||||||
|
|
||||||
## Required E2E repository pipeline
|
## Required E2E repository pipeline
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Journey repository contract
|
# Journey repository contract
|
||||||
|
|
||||||
The UAT repository is a standalone pnpm/Playwright project. It contains no Kubernetes, Helm, Argo CD, application implementation, image publication, or deployment logic.
|
The UAT repository is a standalone pnpm/Playwright project and the authoritative home for functional non-unit tests. It may contain source-coupled integration, browser, database-backed, performance, acceptance, and deployed-environment suites. It contains no application implementation, image/container publication validation, Helm installation/rendering, deployable Kubernetes/Helm desired state, image publication, Argo CD mutation, or deployment logic.
|
||||||
|
|
||||||
## Required baseline
|
## Required baseline
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user