erabo/spiegel_podman
1
0
Fork 0
mirror of https://github.com/podman-container-tools/podman.git synced 2026-10-21 13:27:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
spiegel_podman/test
History
baude 6ce70a33c5 Inspect output should be in array form 
Inspect should be able to inspect one or more containers depending
on the user input.  Therefore, inspect output should be in array
format so the consumer could potentially iterate it.  This PR allows
users to specify one more or containers|images|or a mix for
inspection.  The output, as stated, is therefore in array form.  This
holds true even for a singular image.

In the case that the user enters an invalid container|image "name", we
handle that gracefully.  Podman will output json for the valid names
until it reaches the invalid one.  For example:

In this case, podman will out the json for alpine and then print an
error about 123 being invalid.  It will not continute onto busybox.
This behavior imatates docker.

This addresses issue #360

Signed-off-by: baude <bbaude@redhat.com>

Closes: #371
Approved by: baude
2018-02-21 14:22:36 +00:00
..
bin2img Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
build Initial podman build 2017-12-23 11:47:33 +00:00
checkseccomp Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
copyimg Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
e2e Inspect output should be in array form 2018-02-21 14:22:36 +00:00
hooks Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
testdata Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
demos.sh Match podman inspect output to docker inspect 2018-02-06 19:31:55 +00:00
policy.json Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
README.md Update pause tests per QE suggestions and move to gingko 2018-02-08 22:14:36 +00:00
redhat_sigstore.yaml Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
registries.conf Initial checkin from CRI-O repo 2017-11-01 11:24:59 -04:00
test_podman_build.sh Initial podman build 2017-12-23 11:47:33 +00:00

README.md

Integration testing

Our primary means of performing integration testing for libpod is with the Ginkgo BDD testing framework. This allows us to use native Golang to perform our tests and there is a strong affiliation between Ginkgo and the Go test framework.

Installing dependencies

The dependencies for integration really consists of three things:

  • ginkgo binary
  • ginkgo sources
  • gomega sources

The following instructions assume your GOPATH is ~/go. Adjust as needed for your environment.

Installing ginkgo

Fetch and build ginkgo with the following command:

GOPATH=~/go go get -u github.com/onsi/ginkgo/ginkgo

Now install the ginkgo binary into your path:

install -D -m 755 "$GOPATH"/bin/ginkgo /usr/bin/

You now have a ginkgo binary and its sources in your GOPATH.

Install gomega sources

The gomega sources can be simply installed with the command:

GOPATH=~/go go get github.com/onsi/gomega/...

Running the integration tests

You can run the entire suite of integration tests with the following command:

GOPATH=~/go ginkgo -v tests/e2e/.

Note the trailing period on the command above. Also, -v invokes verbose mode. That switch is optional.

You can run a single file of integration tests using the go test command:

GOPATH=~/go go test -v tests/e2e/libpod_suite_test.go tests/e2e/your_test.go

Run all tests like PAPR

You can closely emulate the PAPR run for Fedora with the following command:

make integration.fedora

This will run lint, git-validation, and gofmt tests and then execute unit and integration tests as well.