github.com/adnan-c/fabric_e2e_couchdb@v0.6.1-preview.0.20170228180935-21ce6b23cf91/bddtests/peer_rest.feature (about)

     1  #
     2  # Test REST API Features of Peers
     3  #
     4  # Tags that can be used and will affect test internals:
     5  #  @doNotDecompose will NOT decompose the named compose_yaml after scenario ends.  Useful for setting up environment and reviewing after scenario.
     6  #  @chaincodeImagesUpToDate use this if all scenarios chaincode images are up to date, and do NOT require building.  BE SURE!!!
     7  @preV1
     8  Feature: Peer REST API
     9      As a Fabric developer
    10      I want to verify REST API behavior
    11  
    12      Scenario: 1 peer and 1 membersrvc, query transaction certs with query parameter count
    13        Given we compose "docker-compose-rest.yml"
    14        And I use the following credentials for querying peers:
    15          | peer | username   | secret       |
    16          | vp0  | test_user0 | MS9qrN8hFjlE |
    17        And I register with CA supplying username "test_user0" and secret "MS9qrN8hFjlE" on peers:
    18          | vp0 |
    19  
    20        When I request transaction certs with query parameters on "vp0"
    21          | key   | value |
    22          | count | 1     |
    23        Then I should get a JSON response with "1" different transaction certs