Open
Description
Currently trying to run tests while the development (or production) environment is running fails for both tmc-server and tmc-sandbox. The test environment configures its own instance of tmc-comet and tmc-sandbox, and tmc-sandbox starts dnsmasq and squid on ports that are not easy to change.
Particularly dnsmasq is problematic since DNS must always run on the standard port, AFAIK.
It may be possible to have the test environment detect running instances of the problematic services and assume/hope they are correctly configured instead of starting its own instances.