How to solve problems running autotests from Teamcity locally?

Question

Continuous Integration

Good day everyone. Perhaps the question will sound naive, but still. There is a problem, which is as follows: to test our applications (banking services), we use autotests in the company that we run in Teamcity. A typical autotest looks something like this: we build two different versions of the application (C++), run them, run two utilities in parallel: one acts as a data provider, the other as a data receiver. Then we use pytest to analyze the results. From time to time it becomes necessary to run a test locally on your machine. At the same time, a huge number of problems arise with the transfer of environment variables from Timcity, problems with the paths to the necessary files, etc. In this connection, the question arises: are there solutions for such cases that make this process as simple as possible, "

Answer 1

And what's the problem with making the local environment the same as in teamcity?
Keep the same directory structure.
Store all the main variables not in Team City but directly in the code, make several configuration files / folders for different environments, including a local profile.
Even passwords can be stored in code if you encrypt and store locally / in Team City only the master key for the desired environment.
Or yes, deal with containers, but this is not always convenient