Do not use FailFast in MDSAL northbound test suite

The MDSAL northbound tests each take only a few tenths of
second to execute no matter whether passing or failing
(unless things in ODL get awry) so there is no benefit from
FailFast. Actually, the FailFast suite tends to mask bugs
as the tests after the first failure won't run at all.

So remove the FailFast support from the MDSAL northbound
test suite.

Change-Id: Ieae3cb87eee678b6e64c18c91cdb93849d4a2915
Signed-off-by: Jozef Behran <jbehran@cisco.com>

diff --git a/csit/suites/netconf/MDSAL/northbound.robot b/csit/suites/netconf/MDSAL/northbound.robot
index 800db68d9d3d630f3b3fbf69769c4dad40a51d1f..87926f467c8b8f0bef71b4e27e62a55650cdee30 100644 (file)
--- a/csit/suites/netconf/MDSAL/northbound.robot
+++ b/csit/suites/netconf/MDSAL/northbound.robot
@@ -23,8 +23,7 @@ Documentation     Metconf MDSAL Northbound test suite.
 ...               TODO: Change the 4 testcases to use unique message IDs.
 Suite Setup       Setup_Everything
 Suite Teardown    Teardown_Everything
-Test Setup        SetupUtils.Setup_Test_With_Logging_And_Fast_Failing
-Test Teardown     FailFast.Start_Failing_Fast_If_This_Failed
+Test Setup        SetupUtils.Setup_Test_With_Logging_And_Without_Fast_Failing
 Library           RequestsLibrary
 Library           SSHLibrary
 Resource          ${CURDIR}/../../../libraries/FailFast.robot