| Library scope: | GLOBAL |
|---|
DOMDataBroker testing: Common keywords
Copyright (c) 2017 Cisco Systems, Inc. and others. All rights reserved.
This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html
This resource file implements various test cases templates. FIXME: add a link to a document (when published) where the scenarios are defined
TODO: When checking first response in isolation scenarior, make sure it comes from the expected member.
Change status use-tell-based-protocol to True or False
Extract first item from the list, third item of the tuple and call TemplatedRequests to check the http status code.
Implements clean leader shutdown test scenario.
Implements clean leader shutdown test scenario.
Implements client isolation test scenario.
Implements client isolation test scenario.
Create prefix based shard with replicas on all nodes
Implements explicit leader movement test scenario.
Implements explicit leader movement test scenario.
Return indexes for clean leader shudown test case, index where transaction producer shoudl be deployed and a shard leader index.
Return indexes for explicit leader movement test case, indexes of present to next leader node and index where transaction producer should be deployed.
Return number of seconds remaining to ${date_in_future}.
The leader isolation test case end if the heal happens within transaction timeout. All write transaction producers shoudl finish without error.
Implements leader isolation test scenario.
Implements leader isolation test scenario.
Implements listener stability test scenario for prefix-based shards.
Implements listener stability test scenario for module-based shards.
The leader isolation test case end. The transaction producer on isolated node should fail and should be restarted. Then all write transaction producers should finish without error.
Verify if write-transaction failed.
Verify that no write-transaction rpc finished, means they are still running.
The leader isolation test case end. The transaction producer on isolated node shoudl fail and should be restarted. Then all write transaction producers shoudl finish without error.
Remove prefix based shard with all replicas
Stop every odl node and start again.
Verify that shard is removed. Jolokia return 404 for shard memeber.