[IO-1335][internal] E2E setup and teardown

[owencjones]

Problem

Need to be able to run E2E tests with appropriate setup and teardown in place

Solution

Added setup, teardown, config, and data seeding functions.

Changelog

Added data seeding
Added Setup functions
Added teardown functions
Added pytest configuration functions
Added before and after run hooks

[linear]

IO-1335 E2E Setup task

Write a pytest setup function to setup and seed data beforehand with example datasets in place etc.

No need to have a lot of data in place, mainly one or a few of each major data types:

• Datasets
• Items

Creation should run on whatever server is setup in the test config task. IO-1334

Ideally, do this with plain HTTP calls, so that if this fails, it's obviously a broken setup task, not darwin-py

Acceptance Criteria

• Optionally, a test team has been created, see IO-1336
• 3 Datasets have been created
• 3 items have been added to each dataset.

Note

This is largely to be expanded on later, when actual tests are being written, so limit it to the above for now. The only variable should be whether the test team is created, so pros and cons in https://www.notion.so/v7labs/E2E-Testing-setup-a22f058e207447ae8dd0b9fa4d368e22

[owencjones]

Normally a very bad practice, this is one of the few exceptions, as this function can only run once in scope. It's also the only way to solve this issue without storing the item in a custom format, and this is not pickleable.

[owencjones]

Normally a very bad practice, this is one of the few exceptions, as this function can only run once in scope. It's also the only way to solve this issue without storing the item in a custom format, and this is not pickleable.

[owencjones]

Sleep is also usually bad, but for test setup to account for latency, it's that or polling.

[Nathanjp91]

So is the intendid use here for a test something along the lines of

def test_upload():
    pytest_sessionstart()
    run_workflow_I_want_to_test()
    pytest_sessionfinish()
    

If so, perhaps should add it as a decorator that does startup and teardown

@e2e.basic
def test():
    run_workflow_I_want_to_test()

[owencjones]

So is the intendid use here for a test something along the lines of

def test_upload():
    pytest_sessionstart()
    run_workflow_I_want_to_test()
    pytest_sessionfinish()
    

If so, perhaps should add it as a decorator that does startup and teardown

@e2e.basic
def test():
    run_workflow_I_want_to_test()

Nah, pytest automatically runs the pytest_sessionstart and pytest_sessionfinish in the conftest.py file at the start and end of the test run, so these will happen before and after running all tests (but not each test) respectively.

TBH, Pytest is maybe not perfect for this kind of integration testing but it can be persuaded into it effectively, and given we are already familiar with it elsewhere, it seems to make better sense.