[PATCH] support: Introduce new subdirectory for test infrastructure

[Stefan Liebler]

Hi Florian,

I've observed a new test-failure string/tst-strcoll-overflow after this 
patch has been commited.

The test uses:
#define TIMEOUT 300
#define EXPECTED_SIGNAL SIGALRM
#define EXPECTED_STATUS 0

With the old test-skeleton, it either timed out or strcoll returned in 
time and do_test returns 0. The test passes as WEXITSTATUS (status) == 
EXPECTED_STATUS.

With the new test-driver, the out-file contains:
0
Expected signal 'Alarm clock' from child, got none

If do_test would return e.g. 2 and EXPECTED_STATUS is defined to 2, the 
test would pass. But if the testcase is then called with --direct, it 
would return 2 instead of 0!

Shall the new test-driver be able to handle this case?

Bye
Stefan