Skip to content

Proposal: Run more tests in e2e-extended #2869

Open
@tanya-borisova

Description

Description

As a TRE Product Owner
I want to run a wide set of tests regularly
So that I have confidence that critical user workflows are being regularly tested and are not degrading over time

With work done in #2838, it should now be possible to run more tests in parallel, without making the total running time prohibitively long.
At the same time, if tests are kept in a separate suite, the wouldn't be required to pass on each PR build

Proposal

Add a new group of tests for the following:

  • test_shared_services.py::test_patch_firewall
  • test_shared_services.py::test_create_shared_service[tre-shared-service-gitea]
  • test_workspace_services.py::test_create_guacamole_service_into_base_workspace
  • test_workspace_services.py::test_create_guacamole_service_into_aad_workspace
  • test_airlock.py::test_airlock_flow
  • test_performance.py::test_bulk_updates_to_ensure_each_resource_updated_in_series
  • test_performance.py::test_parallel_resource_creations

(The last one might be debatable as because tests now run in parallel, parallel resource creation is being tested implicitly anyway).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    e2e-testsE2E testsstoryStories are the smallest unit of work to be done for a project.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions