Test file re-organization

[AlanCoding]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that dispatcher is open source software provided for free and that I might not receive a timely response.

Feature type

Enhancement to Existing Feature

Feature Summary

This proposes a change to organization of files inside of tests/ folder in this repo.

My main reason for doing this is because of painful limitations of pytest-asyncio that I wasn't aware when I started. Most of my time writing tests have been debugging the test event loop, as opposed to any meaningful debugging of the service.

• tests/integration/ --> tests/asyncio/ these are tests using pytest-asyncio
• tests/integration/ --> a new suite that runs the server in a subprocess, which is connected to what I was saying in Add dispatcher/testing/ utilities to help testing with no pg_notify #9, and also the method I expect to be used in the DAB app
• tests/benchmark/ --> patch at Benchmark tests #55, this also runs the server in a subprocess, and hopefully we can merge that with the general fixture. There might be some more complex event exchange through pipes to do this.
• tests/data/ --> exists, has stuff that tests target
• tests/unit/ --> exists, tests that don't need postgres

Ping @Alex-Izquierdo FYI, I have another file moving issue #68

Steps to reproduce

N/A

Current results

No response

Sugested feature result

N/A

Additional information

No response

[Alex-Izquierdo]

Why not simply use tests/integration/sync and tests/integration/async, since they will be integration tests anyway? I don't fully understand the issue at this point. However, if the directory structure is a limitation, an alternative could be tests/integration-sync and tests/integration-async.
My main point is to avoid mixing the test scope with the technology in the directory organization, as they are different concerns.
Also I understand that eventually we would need as well asyncio tests for unit tests, am I wrong?

[AlanCoding]

Oh I assumed asyncio unit tests would just go in tests/unit/. Might be some in there now. Guess I never thought about it.

tests/integration/async would wind up with a lot of nesting.

[AlanCoding]

I also consider the pytest-asyncio tests "inferior", meaning "not true integration" tests. In my head, a subprocess has essentially the full mechanics of a backgrounded dispatcher in-place. The syncio are then "between" unit and integration on the spectrum of how integrated they are.