Using coverage utility exercise more code paths:
- message from channel with wrong type;
- remove message from channel with already removed reader;
- init message from channel (ignored);
- data from devices, ADPU;
- error from device;
- messages split in different ways;
- invalid reader_id values.
Signed-off-by: Frediano Ziglio <fziglio@redhat.com>
Acked-by: Victor Toso <victortoso@redhat.com>
What is here
============
This directory will contain a testsuite for the server.
You can run all the tests and use libtool to debug any of them:
libtool --mode=execute gdb test-just-sockets-no-ssl
Overview of tests
=================
test-just-sockets-no-ssl
A complete server, only provides the main and inputs channels. Doesn't actually produce anything on the channels. Essentially a test of the regular link code (reds.c), good for multiple connect/disconnect tests.
test-empty-success
tests calling
test-fail-on-null-core-interface
should abort when run (when spice tries to watch_add)
basic-event-loop.c
event loop to provide core interface.
Automated tests
===============
test-display-streaming.c
this test can be used to check regressions. For this, test-display-streaming needs to be called passing --automated-tests as parameter