Refactor test to implement asyncio run and test error detection instead of False being return

[MaxenceGui]

Issue description

Currently, the tests for the backend contain code maintenance issues and some wrong test assertions. The use of the asyncio loop makes it difficult to maintain and understand the code while the unsuccessful test looks for a return False statement instead of an exception raised by the function that is being tested.

Work to do

• Use the run function from asyncio to collect the result from the asyncio function.
• Change the unsuccessful function to assertRaise instead of assertEqual

Acceptance criteria

1. The test functions do not manually create a new loop before running a test
2. assertRaise exception instead of assertEqual for a False return

Tasks

• [ ] Modify test_azure_storage_api to test raise Errors from azure_storage_api module
• [ ] Modify the test to use aynscio.run instead of an async loop.

[sylvanie85]

Is that issue still relevant ? The tests already all use asyncio.run() and there is already assertRaise in the unsuccessful tests.

What do you think ? @ChromaticPanic @Francois-Werbrouck

[Francois-Werbrouck]

We are not using the azure_storage_api module anymore, also once #61 is merged, most functions return will already have been modified. I'd wait for the merge to double check all functions before officially closing this issue (if no-one else see's a problem with closing this)