[INTTEST-28] Contract with releng/builder parts of CSIT: define and verify Created: 03/Dec/15 Updated: 19/Oct/17 |
|
| Status: | Confirmed |
| Project: | integration-test |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
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. 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. Check_Whether_Netconf_Connector_Works test case of "netconfready" suite reports immediate failure, citing this Bug as the reason. For more background, see comments in https://git.opendaylight.org/gerrit/26446 |
| Comments |
| Comment by Jozef Behran [ 20/Jan/16 ] |
|
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 https://git.opendaylight.org/gerrit/33083/). 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. |