[GSK-2159] Using a subprocess for pytest

[Hartorn]

Description

Related Issue

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[kevinmessiaen]

Look good to me, that's a shame that we have to do this

[linear]

GSK-2159 Add a way to handle memory leak in pytest

At the moment, we are splitting the tests to avoid memory usage explosion

what we could do would be to twist a bit pytest-xdist, to make to stop and restart the workers it's using base on memory usage or number of tests ran.

Any way to make the tests run fine is ok, so it may not be the only solution

https://pypi.org/project/pytest-xdist/

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information