-
Notifications
You must be signed in to change notification settings - Fork 10
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
MIW | E2E-testing for MIW with EDC >0.8.0 #822
Comments
@OSchlienz not sure about this feature. Is it planned to present it in tomorrow's planning? It was never presented in a Refinement meeting. Did we miss something? |
The adjustments needed aren't limited to testing:
|
Added MIW label |
Moved to backlog |
@stephanbcbauer i assume based on the last discussions we will not find a contributor/committer for this topic ? should we close it ? |
Fine for me… it's not deleted … in case we need it, we can reopen it. THX |
Description
The purpose of this ticket is to place the need for a separate e2e test for MIW.
Background information: MIW does not partipate in E2E-testing for 24.08 which is taking place with EDC version 0.7.3. and DIM wallet. For IATP support, MIW requires sts remote client and oauth2 client in EDC, which were introduced in EDC 0.8.0.
On the other hand, currently no multi wallet support is possible (a concept for multi wallet support & BYOW is expected for R24.12.)
Under these circumstances a parallel test environment or a temporary use of the existing environment is needed in order to perform e2e tests for MIW which should cover the entire onboarding sequence where the wallet is a part of.
The following components are required to cover the onboarding/registration sequence for e2e-tests:
Required steps:
Impact
Additional effort for setting up components in a parallel test environment and performing tests. Using the existing environment would lead to a temporary unavailability for possible other tests .
Additional information
The text was updated successfully, but these errors were encountered: