more automated tests

[Antoine Martin]

Follow up from #177, see also #660 - in particular things like #822.

• integration tests: we want some tests that start a server and connect to it.

Shadow server, normal server, proxy, etc... Even the tcp proxy can be exercised this way.
Concurrent connections (spawn 10 xpra info?), etc.

Here's a tricky one that I would like to be able to catch with some tests, but it is going to be HARD: r8604 broke nvenc4 + nvenc5 with the proxy server only (fixed by r9413 + backport in r9414).

• client rendering tests: we should be able to fire up a virtual display, create a window (try both pixmap and opengl backends) and paint on it (no client class involved), then check that no errors or exceptions were triggered.

• this one would be hard to check for: #867

[Antoine Martin]

(fix milestone - too late for 0.15)

[Antoine Martin]

I don't see how this can easily be automated, but it would be nice to catch bugs like #926 automatically.

[Antoine Martin]

And also catch things like: #1031

[Antoine Martin]

Milestone renamed

[Antoine Martin]

Milestone renamed

[Antoine Martin]

As of r14869 + r14868 + r14867 + r14866, the unit tests have been improved, most run with both python2 and python3 and we now also run the tests as part of the build process for win32 (r14870) and osx (r14871)!

@smo: FYI, feel free to just close.

[Antoine Martin]

For reference, the latest run scripts allow us to pass a specific unit test to run (useful for debugging), and the following environment variables are also useful:

DELETE_TEMP_FILES=0 \
XPRA_ALL_DEBUG=1 \
XPRA_TEST_DEBUG=1 \
    ./run2 ./unit/server/server_sockets_test.py