mirror of https://github.com/containers/podman.git synced 2025-10-12 16:56:32 +08:00

Files

Daniel J Walsh a3156da21c podman exec should handle options --env foo

If the user does not specify foo=bar, then the exec code should
look for the foo environment variable in its environment and pass it
in.  This is the way podman run works.

Also added tests to make sure this all works.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

Closes: #552
Approved by: mheon

2018-03-26 23:27:00 +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

podman exec should handle options --env foo

2018-03-26 23:27:00 +00:00

hooks

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

make shell: build, test and run in a container

2018-03-13 17:18:23 +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_baseline.sh

Add toggle for Docker install/deinstall for baseline test

2018-03-08 07:23:16 +00: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 test/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 test/e2e/libpod_suite_test.go test/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.

Run tests in a container

In case you have issue running the tests locally on your machine, you can run them in a container:

make shell

This will run a container and give you a shell and you can follow the instructions above.