microsoft / microsoft/AzureTRE

Proposal: Run more tests in e2e-extended

Open
#2,869 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

e2e-tests story
Dominant language
Python
Stars
235
Forks
192
Avg merge
1d 23h
Merged PRs (30d)
13

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 https://github.com/microsoft/AzureTRE/issues/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).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating how the e2e-extended test group is configured, then inspect the listed tests in test_shared_services.py, test_workspace_services.py, test_airlock.py, and test_performance.py. Add the proposed tests to that separate group and verify that they run in parallel without being required on each PR build.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.