Sha256: 495b07aa4db2977b57ccf22ad27019cf535630d84c4f2fea94dbbb6b692abeb8

Contents?: true

Size: 1.26 KB

Versions: 7

Compression:

Stored size: 1.26 KB

Contents

@api_server
Feature: test server
  In order to have easy integration with my test code
  As a ruby developer
  I want to have a client library take care of starting/stopping an instance of rest-assured

  Scenario: start rest-assured server
    Given there is free tcp port
    When I start rest-assured server via client library:
    """
    RestAssured::Server.start(:port => @free_tcp_port)
    """
    Then rest-assured server should be running:
    """
    expect(RestAssured::Server.up?).to eq true
    """

  Scenario: start asyncronously (so that other heavy setup - e.g. firefox startup - can be done in parallel)
    Given there is free tcp port
    When I start rest-assured asyncronously:
    """
    RestAssured::Server.start!(:port => @free_tcp_port)
    """
    Then rest-assured server should not be running:
    """
    expect(RestAssured::Server.up?).to eq false
    """
    When it finally comes up
    Then rest-assured server should be running:
    """
    expect(RestAssured::Server.up?).to eq true
    """

  Scenario: stop rest-assured server
    Given rest-assured has been started via client library
    When I stop it:
    """
    RestAssured::Server.stop
    """
    Then it should be stopped:
    """
    expect(RestAssured::Server.up?).to eq false
    """

Version data entries

7 entries across 7 versions & 1 rubygems

Version Path
rest-assured-4.0.0 features/ruby_api/test_server.feature
rest-assured-3.0.1 features/ruby_api/test_server.feature
rest-assured-3.0.0 features/ruby_api/test_server.feature
rest-assured-2.2.0 features/ruby_api/test_server.feature
rest-assured-2.1.0 features/ruby_api/test_server.feature
rest-assured-2.0.2 features/ruby_api/test_server.feature
rest-assured-2.0.1 features/ruby_api/test_server.feature