Sha256: bb15881d5aeb30254cb5a0b311c46bf1709ae5115f61dce4fb26ebabbac2ab74
Contents?: true
Size: 1.53 KB
Versions: 11
Compression:
Stored size: 1.53 KB
Contents
@announce-output Feature: Testing Background: Given I successfully run `env DEBUG=true GLI_DEBUG=true debify package -d ../../example -v 0.0.1 example -- --post-install /distrib/postinstall.sh` Scenario: 'example' project can be tested successfully When I successfully run `env DEBUG=true GLI_DEBUG=true debify test -t 4.9-stable -v 0.0.1 -d ../../example --no-pull example test.sh` Then the stderr should contain "Test succeeded" Scenario: 'example' project can be tested when linked to another container Given I start a container named "other_host" When I successfully run `env DEBUG=true GLI_DEBUG=true debify test -t 4.9-stable -v 0.0.1 -d ../../example --no-pull --link other_host example net-test.sh` Then the stderr should contain "Test succeeded" Scenario: 'example' project can be tested on a network other than the default Given I start a container named "other_host" on network "test-net" When I successfully run `env DEBUG=true GLI_DEBUG=true debify test -t 4.9-stable -v 0.0.1 -d ../../example --no-pull --net test-net example net-test.sh` Then the stderr should contain "Test succeeded" Scenario: 'example' project can be tested on a network other than the default with a host aliased Given I start a container named "another_host" on network "test-net" When I successfully run `env DEBUG=true GLI_DEBUG=true debify test -t 4.9-stable -v 0.0.1 -d ../../example --no-pull --link another_host:other_host --net test-net example net-test.sh` Then the stderr should contain "Test succeeded"
Version data entries
11 entries across 11 versions & 1 rubygems