Nexent Test Assets
Create and maintain Nexent's repository-owned feature catalog, D1-D5 case-local...
Install
npx skills add ModelEngine-Group/nexent --skill nexent-test-assets -g -a claude-code -y- Repository
- ModelEngine-Group/nexent6.1k
- Category
- Documents
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 2,104 tokens
- Runs scripts
- No, instructions only
What it does
Create and maintain Nexent's repository-owned feature catalog, D1-D5 case-local contracts and fixed scripts, change records, generated execution registry and Excel view. Use for requirements, bug regressions, post-development test backfill, test implementation, and formal asset migration. Traditional UT uses nexent-python-tests.
Nexent formal test assets
Maintain one traceable chain:
Requirement or Bug -> Feature -> D1-D5 Case -> case-local execution.yaml -> Fixed Script -> Result.
Paths are relative to the repository root. Authoritative assets live under test-e2e/features/<Feature-ID>/feature.yaml, test-e2e/cases/<Case-ID>/case.yaml, and test-e2e/changes/<type>/. Each implemented Case owns execution.yaml and its primary test script in the same Case directory. features/<Feature-ID>/cases.md, test-e2e/infra/generated/registry.json, and the Excel workbook there are generated read-only views; no hand-maintained central manifest or cross-platform symlink is needed.
