-
Notifications
You must be signed in to change notification settings - Fork 148
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
Extended e2e for all shared, workspaces, and workspace services #1921
Comments
Nexus on VM is correctly blocked from being E2E tested as it doesn't use the pipeline method for firewall changes. This is its story: #2328 |
@tamirkamara where are we at with this? Thanks. |
Shared services are mostly done, what's not has a mention in the code and issues are opened: |
I'm not sure this is a good idea anymore since running so many templates is actually testing Azure more than the TRE system. The number and frequency of issues we are getting every day would make this test almost useless. |
@tamirkamara don't think they need to run all the time - but need to be able to validate them some how. |
@marrobi after going through e2e test in AzureTRE, many of test has been done so which test you would like to process next? |
Can you take my draft PR, check it works, pases extended tests etc, then we can review and merge. |
As we iterate, and update things like terraform versions, or Azure services are updated regressions are appearing in existing workspace services. Maybe this runs nightly or weekly?
All shared services should be deployed, updated, and deleted as part of the extended e2e tests.
All workspaces should be deployed, updated, and deleted as part of the extended e2e tests.
All workspace services should be deployed, updated, and deleted as part of the extended e2e tests.
The text was updated successfully, but these errors were encountered: