Skip to content

feat: Add CI tests to prevent regressions #22

@OneNormalUsername

Description

@OneNormalUsername

extractor.sh code is complicated, and preventing regressions whenever code is modified or added takes time and effort.

An idea to prevent this would be to add tests so that commits wouldn't be able to be merged unless a sample set of each supported firmware successfully outputs IMGs, and that their hashes match those previously version controlled in this repository.

For A-only OTA, https://otafsg1.h2os.com/patch/amazone2/GLO/OnePlus3TOxygen/OnePlus3TOxygen_28.A.86_GLO_086_1911042121/OnePlus3TOxygen_28_OTA_086_all_1911042121_9156030ead54e.zip can be used.
For Oplus A-only OTA, https://oxygenos.oneplus.net/system_vendor.zip can be used
For A/B OTAs, https://gauss-componentotacostmanual-sg.allawnofs.com/remove-60818dddbcc4ff1e05001dbecdd5a9b3/component-ota/22/03/27/d7a3625cd77440418671588fe07b4a6b.zip can be used.

I will edit content of this issue later to add MD5s of the extracted IMGs.

A problem though is I am unsure how to implement this idea in code, also maybe some of the supported firmware isn't available to download via an anonymous link. There would likely be a need to store it on the machine on which one tests will run to prevent issues such as firmware being unavailable, or downloading extremely slowly, thereby making CI tests run for a long amount of time or fail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions