Tests infrastructure improvement

[ego]

Checked

• I searched existing ideas and did not find a similar one
• I added a very descriptive title
• I've clearly described the feature request and motivation for it

Feature request

As a lazy man, I suppose it would be better to have simple and clear way to contribute.

This is critical for open source - add new features quickly. So the infrastructure around the projects should not complicate the development.

1. Edit code
2. Check it
   make install && make tests

It could be the Docker or usual Python venv as well, but all additional steps like moving to the some specific lib and run its tests lib by lib, setting env vars and so on, should be done under the hood.

Definitely it is better to improve tests documentation
and spend additional time for auto-infra and auto-setups.

Motivation

Newcomers and contributors experience.

Proposal (If applicable)

It could be some main Makefile in the root of repo and docker-compose-test.yaml witch build, run and test all libs at ones.