Fix how the systemTest does not return any result when it forced to quit the test.

If the systemTest forced to quit due to some problem, it quits the test without giving a result to the current case. :
[REPORT] [07 Aug 2017 02:27:46] ONOS service did not start properly on all nodes
2017-08-07 02:27:46,346 - FUNCipv6Intent - WARNING - Assertion Failed
[2017-08-07 02:27:46.346939] [FUNCipv6Intent] [STEP] 2.7: Starting ONOS CLI sessions
2017-08-07 02:28:46,601 - FUNCipv6Intent - INFO - Starting CLI failed. Retrying...
2017-08-07 02:29:16,783 - FUNCipv6Intent - ERROR - Connection to CLI 10.128.20.11 timeout
2017-08-07 02:29:16,783 - FUNCipv6Intent - INFO - ONOS CLI did not start up properly

*************************************
Test Execution Summary
*************************************

Test Start : 07 Aug 2017 02:15:14
Test End : 07 Aug 2017 02:29:16
Execution Time : 0:14:02.706715
Total tests planned : 13
Total tests RUN : 1
Total Pass : 1
Total Fail : 0
Total No Result : 0
Success Percentage : 100%
Execution Result : 7%