Test suite should report IOERR_COPY when shell copy command fails (fixed).
2. Host test shell plugin update
How you can specify with option -c value 'shell' and copy plugin will detect
for you your OS and choose between 'cp' (for 'posix') and 'copy' (for
Windows).
1. Removed globaly initialized data inside class test() function
2. Removed global variables initialization dependency. Any cause some Python
implementations and configurations to fail in runtime
3. Added info about Echo port #7 rationale.
4. Testsed with K64F and network tests:
Test summary:
+--------+--------+---------+----------------------------+--------------------+
| Result | Target | Test ID | Test Description | Elapsed Time (sec) |
+--------+--------+---------+----------------------------+--------------------+
| OK | K64F | NET_1 | TCP client hello world | 3.26 |
| OK | K64F | NET_13 | TCP client echo loop | 2.05 |
| OK | K64F | NET_2 | NIST Internet Time Service | 3.43 |
| OK | K64F | NET_3 | TCP echo server | 1.54 |
| OK | K64F | NET_4 | TCP echo client | 1.54 |
| OK | K64F | NET_5 | UDP echo server | 1.46 |
| OK | K64F | NET_6 | UDP echo client | 1.6 |
| OK | K64F | NET_7 | HTTP client hello world | 3.4 |
| OK | K64F | NET_8 | NTP client | 2.39 |
+--------+--------+---------+----------------------------+--------------------+
Result: 9 OK
Completed in 122.18 sec
Boolean value used to calclate single RTC test PASS / FAIL was not used to
calculate overall result.
==== ISSUE ====
The test suite treats the RTC test as successful, but test itself reports
failures. Which one is correct – does it fail or does it pass? See below:
HOST: Run test...
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 4.02 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.04 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.04 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.03 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.04 sec... FAIL
{{success}}
{{end}}
Test::Output::Finish
TargetTest::ARM_MPS2_M4::ARM::MBED_16::RTC [OK] in 30.37 of 40 sec
==== FIX ====
HOST: Run test...
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 0.04 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.04 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.04 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.04 sec... FAIL
MBED: [0] [1970-01-01 00:00:00 AM]
HOST: [0] [1970-01-01 00:00:00 AM] received time +0 sec after 1.04 sec... FAIL
{{failure}}
{{end}}
Host test plugins: Increased test suite timeout on each test execution twice - for now, so tests do not timeout. TODO: exclude coopy and reset procedures from testcase timeout measurement
Host test plugins: Added 'stable' attribute to each plugin, by default all plugins are not stable
Moved all MPS2 related functions to MPS2 plugins in host test directory
Przemek Wirkus
Martin Kojtal
Mihail Stoyanov