repeat unit tests name and status at end of test log

[s-celles]

Hello,

When facing a very long test log it's can be hard to find what test files are failling
(especially when errors are very long such as in this build https://travis-ci.com/scls19fr/mwe_arduino_ci/builds/97293666 )

Providing a more readable end of log will be great (such as this one)

Unit testing test_mwe_00.cpp with g++                                          ✗
Unit testing test_mwe_01.cpp with g++                                          ✗
Unit testing test_mwe_02.cpp with g++                                          ✗
Unit testing test_mwe_03.cpp with g++                                          ✗
Unit testing test_mwe_04.cpp with g++                                          ✗
Unit testing test_mwe_05.cpp with g++                                          ✗
Indexing libraries...                                                          ✓
Installing library under test...                                               ✓
Library installed at...            /home/travis/Arduino/libraries/mwe_arduino_ci
Requested library example platform 'mega2560' is defined in 'platforms' YML... ✓
Using built-in board package...                                      arduino:avr
Installing board package arduino:avr...                                        ✓
Setting compiler warning level...                                              ✓
Switching to board for mega2560 (arduino:avr:mega:cpu=atmega2560)...           ✓
Verifying mwe_arduino_ci_01.ino...                                             ✓
Verifying mwe_arduino_ci_00.ino...                                             ✓
Found: 6 test files - 5 examples
Failures: 6

Kind regards

PS... that's odd to see only 2 examples here... when there was 5 in previous build
https://travis-ci.com/scls19fr/mwe_arduino_ci/builds/97292804#L748-L752
It seems that it was a delay in Travis log display

[s-celles]

Or an other possible end of log (more human readable)

Unit tests
  Found: 6 test files
  Unit testing test_mwe_00.cpp with g++                                        ✗
  Unit testing test_mwe_01.cpp with g++                                        ✗
  Unit testing test_mwe_02.cpp with g++                                        ✗
  Unit testing test_mwe_03.cpp with g++                                        ✗
  Unit testing test_mwe_04.cpp with g++                                        ✗
  Unit testing test_mwe_05.cpp with g++                                        ✗
Indexing libraries...                                                          ✓
Installing library under test...                                               ✓
Library installed at...            /home/travis/Arduino/libraries/mwe_arduino_ci
Requested library example platform 'mega2560' is defined in 'platforms' YML... ✓
Using built-in board package...                                      arduino:avr
Installing board package arduino:avr...                                        ✓
Setting compiler warning level...                                              ✓
Switching to board for mega2560 (arduino:avr:mega:cpu=atmega2560)...           ✓
Verifying examples
  Found: 5
  Verifying mwe_arduino_ci_01.ino...                                           ✓
  Verifying mwe_arduino_ci_00.ino...                                           ✓
Failures: 6

[ianfixes]

This depends on #83 because currently the test runner doesn't understand (or even pay attention to) the output of the unit test binaries. I also need a functioning TAP v13 parser in Ruby to accomplish that step.