https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/INTTEST-28 integration-test <p>releng/builder contains bash scripts that do initial environment preparation before starting integration/test Robot suites. But it is not always clear what state of ODL (or environment) should the suites assume.</p> <p>For example, currently the scrips guarantee GET to restconf/modules results in status code 200. But some suites use netconf-connector, which may or may not be ready at that point. And if it is not ready, it is not clear whether suites should wait patiently, or whether they should fail.</p> <p>Check_Whether_Netconf_Connector_Works test case of "netconfready" suite reports immediate failure, citing this Bug as the reason.<br/> The next test case Wait_For_Netconf_Connector than waits patiently, allowing subsequent suites to assume netconf-connector is ready.</p> <p>For more background, see comments in <a href="https://git.opendaylight.org/gerrit/26446" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/26446</a></p> <p>Operating System: All<br/> Platform: All</p> INTTEST-28

Contract with releng/builder parts of CSIT: define and verify

Bug Confirmed Unresolved Unassigned Vratko Polak Thu, 3 Dec 2015 12:29:59 +0000 Thu, 19 Oct 2017 21:29:05 +0000 0 2 <p>Additionally it should be decided whether we want the "Check_Whether_Netconf_Connector_Works" test case in the netconf-readiness suite to be included in the test results (change <a href="https://git.opendaylight.org/gerrit/33083/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/33083/</a>). The argument for this change is that when the contract says "the parts must provide a way to detect whether they are ready", then the testcase detects a breach of this contract and therefore it shall be included.</p> Development Rank 0|i01lkv: