test: add upgrade home fixture coverage
This commit is contained in:
parent
1a6d9db913
commit
3fbd64f131
3 changed files with 120 additions and 4 deletions
|
|
@ -308,12 +308,15 @@ Goal: make first deployment the start of a controlled compatibility story.
|
|||
`cargo run`.
|
||||
- `[x]` Archives include relevant docs and license files.
|
||||
|
||||
- `[ ]` Add upgrade tests.
|
||||
- `[x]` Add upgrade tests.
|
||||
Acceptance criteria:
|
||||
- `[ ]` Fixture homes from previous tagged pre-releases migrate forward.
|
||||
- `[ ]` Upgrade tests include store schema, config, keychain/auth logs, CAS
|
||||
- `[x]` Fixture homes from previous tagged pre-releases migrate forward.
|
||||
There are no tagged pre-releases yet, so the current test uses a synthetic
|
||||
pre-release home and the release policy requires retaining real tagged
|
||||
fixture homes once tags exist.
|
||||
- `[x]` Upgrade tests include store schema, config, keychain/auth logs, CAS
|
||||
metadata, and peer cards.
|
||||
- `[ ]` Rollback expectations are documented.
|
||||
- `[x]` Rollback expectations are documented.
|
||||
|
||||
- `[x]` Publish release and support policy.
|
||||
Acceptance criteria:
|
||||
|
|
|
|||
Loading…
Reference in a new issue