How to organize test benches?

Question

System administration

Now we have a production server and develop where we test our branches (features), and now we are faced with a problem when we need to test different branches at the same time. How can the development and testing process be organized so that there are no conflicts between developers and testers when switching branches?
The project consists of 3 services under docker, the whole project is assembled through docker-compose, I tried to find some solution for flexible deployment of a test stand for branches, and after testing the stand would simply be deleted but found nothing.

Answer 1

Too little information to answer the question.
Presumably, the scheme can be as follows:
Use Gitlab CI (for example)
There are scenarios in which a test is needed (for example, pushing to a branch)
So let the container with the necessary branch rise when pushing ( gitlab ci can do this), then tests and then deleting by trigger or time - as you like.
Problems can be at the stage of shared external resources or ports - nothing is said about this.
Well, or you can use ansible, for example, raise a demo virtual machine - for example, ansible can create virtual machines on vmware, raise a container on it, then extinguish the virtual machine by some kind of trigger or at the beginning of the next gitlab job.

Answer 2

Aleksey Sharapov 's option is the best.
We, for example, still use the classic method (because not all projects are containerized).
There are 4 fixed test environments distributed across development and test teams. Each of the teams wants projects or branches, and these are rolled out to these environments through Jenkins.