Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go/oasis-test-runner: Refactor e2e tests #5265

Merged
merged 9 commits into from May 24, 2023

Conversation

peternose
Copy link
Contributor

@peternose peternose commented May 22, 2023

Base changes for E2E upgrade tests.

go/oasis-test-runner/scenario/e2e/e2e.go Outdated Show resolved Hide resolved
@peternose peternose force-pushed the peternose/internal/upgrade-tests-refactoring branch 3 times, most recently from 45f9379 to 75cfa06 Compare May 23, 2023 23:14
In SGX mode, it is essential to refresh the runtime bundles before
configuring the key manager runtime's policy. This ensures that
the policy includes the most up-to-date enclave IDs.
The runtime test clients have been consolidated into a more robust
client capable of executing arbitrary key/value runtime scenarios.
This enhancement gives E2E tests greater control over the operations
being tested.
The runtime fixture configuration has been updated to allow the retention
of runtime bundles after the completion of an E2E scenario.
The flags for specifying the runtime source and target directories
have been moved from the trust root scenario to the runtime scenario.
This change simplifies the buildkite scripts and enables all runtime
scenarios to utilize these folders in their tests.
The implementation of the runtime scenario and some of its methods
have been made public, allowing them to be used in E2E tests outside
of this repository.
The scenarios e2e.E2E and runtime.RuntimeImpl were renamed to e2e.Scenario
and runtime.Scenario, respectively, to address stuttering issues when used
by other packages.
The key manager upgrade scenario has been refactored to retrieve
the entity's nonce and the key manager's old deployments from
the consensus layer. This modification enables the test to be used
in cross-version test scenarios, where the nonce and the deployments
are defined in the pre-upgrade scenario.
@peternose peternose force-pushed the peternose/internal/upgrade-tests-refactoring branch from 75cfa06 to 28622d3 Compare May 24, 2023 13:41
@peternose peternose merged commit 9287700 into master May 24, 2023
3 checks passed
@peternose peternose deleted the peternose/internal/upgrade-tests-refactoring branch May 24, 2023 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants