anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reorder ATVM status output and standardize push reminders

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 11:57:19 -04:00
parent 4b04f9b49d
commit c60542e0e5
5 changed files with 36 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
atvm/docs/automation/status-template.md
View File

@@ -10,16 +10,6 @@ Use this as the default ATVM automation run-status template for:
## ATVM Run Status
### <build_name>
**COVERAGE:**
- template: `<template-name>`
- datastore/config family: `<config family>`
- migration style: `<high-level test style>`
- integration/plugin path: `<integration/plugin>`
- scope of this run: `<batch or run scope>`
**TEST FLOW:**
- <template-specific numbered steps>
**SUMMARY:**
| Metric | Value |
@@ -49,13 +39,23 @@ Use this as the default ATVM automation run-status template for:
| longest | <host> - <runtime> or n/a |
| average | <runtime> or n/a |
**COVERAGE:**
- template: `<template-name>`
- datastore/config family: `<config family>`
- migration style: `<high-level test style>`
- integration/plugin path: `<integration/plugin>`
- scope of this run: `<batch or run scope>`
**TEST FLOW:**
- <template-specific numbered steps>
**NOTES:**
- <note>
- <note>
```
## Rules
- Keep `COVERAGE:`, `TEST FLOW:`, `SUMMARY:`, `HOSTS:`, `TIMING:`, and `NOTES:` in that order.
- Keep `SUMMARY:`, `HOSTS:`, `TIMING:`, `COVERAGE:`, `TEST FLOW:`, and `NOTES:` in that order.
- Use the title format:
- `## ATVM Run Status`
- `### <build_name>`