Skip to content

WORKFLOW: Automatically test importing save files from old versions #1793

Open
@catloversg

Description

@catloversg

In #1790, we fixed a bug related to migration code. Currently, our CI workflows do not test importing save files from old versions. In risky PRs, d0sboots has to manually test it manually. It's best to implement a workflow doing it automatically for each PR.

My plan:

  • Use an E2E testing framework (Selenium, Cypress, etc.) to simulate loading save files and check regression bugs (Recovery mode UI, exception alert popup, etc.)
  • Generate testing save files from old versions. d0sboots has a collection of user-provided save files, but using them publicly in a testing workflow is risky due to potential licensing issues. It's best to create our own collection.

This plan is fairly low on my priority list, so I created this issue to make sure that I don't forget about it (or procrastinate too much).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    operational improvementEverything relating to the build process: Github configuration, programming tool configuration files

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions