Skip to content

☂️ Paseo + Kusama AHM Checklist for Testing #161

@kianenigma

Description

@kianenigma

More mission focused version of #124, aiming to give a clear checklist for Paso and Kusama AHM

Tentative fow now and representing what I would do -- please chip in and then we can lock it for Kusama.

To recap, we aim towards a system where on a fixed cadence (nightly?) the following is run in the CI:

  • bite networks and create pre-migration database for RC/AH + try-runtime-snap
  • run the migration
  • create post-migration database for RC/AH + try-runtime-snap
  • Then
    • Use the try-runtime snaps to run post-migration Rust tests
      • We need a test in runtimes/integration-tests/ahm that just does the post-migration rust test + port it to the paseo runtimes too
    • Use the post-migration database to spawn network + run TS tests
    • Use the post migration database to spawn network + run PET

I tried to speculate how the workflow/jobs should be composed, but it not my domain, leaving it to @pepoviola

I named this Paseo + Kusama checklist, as I am not sure if we want to have all things automated as a requirement for Paseo. A faster route to Paseo would be to lock a specific commit of the paseo-runtime (now doable via #160), as soon all steps are verified manually by the owner, we give the green light to do Paseo AHM.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions