So I'm wondering what other people do in this scenario:
- You have an executable that provides a (networked) service
- You want to test against the executable's service
- You want to be able to start/stop the executable during the tests
- You want to be able to run multiple executables between test suites (i.e. with different configs for each suite of tests)
I'm mostly been using subprocess, and this works; but I always seem to wind up with situations where the child process is hung, or winds up running past the execution of the tearDown() for the suite. Any given failure can almost always be fixed, but it always feels messy and low-level, and it just feels like there should be something better.
So, how do *you* run captive servers?
Pingbacks are closed.