Support backwards compatibility tests #1911
Assignees
Comments
This was referenced Aug 8, 2022
9 tasks
|
closing as all supported branches have been updated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Support tests which ensure backwards compatibility
Problem Definition
We currently have some automated E2E tests which test the same version of our simapp against one another. But we don't ensure that new features are backwards compatible in an automated way.
Ensure the simd Dockerfile and build/push workflow exist on all active
release/vX.Y.Zbranches. This will ensure that every released version will have a docker image we can use in E2E tests.v1.4.xchore: adding dockerfile and release task to release/1.4.x #1921v1.5.xchore: adding dockerfile and release task to release/1.5.x #1922v2.1.xchore: adding dockerfile and release task to release/2.1.x #1923v2.2.xchore: adding dockerfile and release task to release/2.2.x #1924v2.3.xchore: adding dockerfile and release task to release/2.3.x #1925v2.4.xchore: adding release task to release/2.4.x #1927v3.0.xchore: adding dockerfile and release task to release/3.0.x #1928v3.1.xchore: adding dockerfile and release task to release/3.1.x #1931v3.2.xchore: adding dockerfile and release task to release/3.2.x #1932Proposal
As a starting point, we can simply provide two environment variables in our Github Workflows to specify different images. One for each chain.
This can be expanded upon to create a larger test matrix.
For Admin Use
The text was updated successfully, but these errors were encountered: