Directories
¶
| Path | Synopsis |
|---|---|
|
Package main provides a tool that scans kubernetes e2e test source code looking for conformance test declarations, which it emits on stdout.
|
Package main provides a tool that scans kubernetes e2e test source code looking for conformance test declarations, which it emits on stdout. |
|
framework
Package framework contains provider-independent helper code for building and running E2E tests with Ginkgo.
|
Package framework contains provider-independent helper code for building and running E2E tests with Ginkgo. |
|
framework/config
Package config simplifies the declaration of configuration options.
|
Package config simplifies the declaration of configuration options. |
|
framework/ginkgowrapper
Package ginkgowrapper wraps Ginkgo Fail and Skip functions to panic with structured data instead of a constant string.
|
Package ginkgowrapper wraps Ginkgo Fail and Skip functions to panic with structured data instead of a constant string. |
|
framework/log
Package log should be removed after switching to use core framework log.
|
Package log should be removed after switching to use core framework log. |
|
framework/podlogs
Package podlogs enables live capturing of all events and log messages for some or all pods in a namespace as they get generated.
|
Package podlogs enables live capturing of all events and log messages for some or all pods in a namespace as they get generated. |
|
framework/testfiles
Package testfiles provides a wrapper around various optional ways of retrieving additional files needed during a test run: - builtin bindata - filesystem access
|
Package testfiles provides a wrapper around various optional ways of retrieving additional files needed during a test run: - builtin bindata - filesystem access |
|
network
Package network are the end-to-end tests for Kubernetes networking.
|
Package network are the end-to-end tests for Kubernetes networking. |
|
upgrades
Package upgrades provides a framework for testing Kubernetes features before, during, and after different types of upgrades.
|
Package upgrades provides a framework for testing Kubernetes features before, during, and after different types of upgrades. |
|
e2e_node contains e2e tests specific to the node TODO: rename this package e2e-node
|
e2e_node contains e2e tests specific to the node TODO: rename this package e2e-node |
|
environment
Build the binary with `go build conformance.go`, then run the conformance binary on a node candidate.
|
Build the binary with `go build conformance.go`, then run the conformance binary on a node candidate. |
|
remote
Package remote contains implementations of the TestSuite interface, which specify how to run various node test suites remotely.
|
Package remote contains implementations of the TestSuite interface, which specify how to run various node test suites remotely. |
|
runner/remote
To run the node e2e tests remotely against one or more hosts on gce: $ go run run_remote.go --logtostderr --v 2 --ssh-env gce --hosts <comma separated hosts> To run the node e2e tests remotely against one or more images on gce and provision them: $ go run run_remote.go --logtostderr --v 2 --project <project> --zone <zone> --ssh-env gce --images <comma separated images>
|
To run the node e2e tests remotely against one or more hosts on gce: $ go run run_remote.go --logtostderr --v 2 --ssh-env gce --hosts <comma separated hosts> To run the node e2e tests remotely against one or more images on gce and provision them: $ go run run_remote.go --logtostderr --v 2 --project <project> --zone <zone> --ssh-env gce --images <comma separated images> |
|
images
|
|
|
pets/peer-finder
A small utility program to lookup hostnames of endpoints in a service.
|
A small utility program to lookup hostnames of endpoints in a service. |
|
test-webserver
A tiny web server that serves a static file.
|
A tiny web server that serves a static file. |
|
Package integration provides integration tests for Kubernetes.Some tests require a running etcd or Docker installation on the system.
|
Package integration provides integration tests for Kubernetes.Some tests require a running etcd or Docker installation on the system. |
|
list all unit and ginkgo test names that will be run
|
list all unit and ginkgo test names that will be run |
|
soak
|
|
|
do a fast type check of kubernetes code, for all platforms.
|
do a fast type check of kubernetes code, for all platforms. |
|
junit
Package junit provides data structures to allow easy XML encoding and decoding of JUnit test results.
|
Package junit provides data structures to allow easy XML encoding and decoding of JUnit test results. |
Click to show internal directories.
Click to hide internal directories.