docker-cli

Files

Doug Davis c8f1332dce Move CLI config processing out from under registry dir

No logic changes should be in here, just moving things around.

Signed-off-by: Doug Davis <dug@us.ibm.com>
Upstream-commit: bb9da6ba9294a8eab8f4dfaf7cf07c57959fe608
Component: engine

2015-04-23 10:18:38 -07:00

fixtures/https

Revert "Dealing with trailing whitespaces"

2015-03-25 10:04:56 -06:00

api_test.go

Merge pull request #12358 from ZJU-SEL/remove_job_from_tag

2015-04-19 16:02:28 -04:00

container_test.go

Decode container configurations into typed structures.

2015-04-15 10:22:07 -07:00

https_test.go

Defer creation of trust key file until needed

2015-01-29 13:46:12 -08:00

README.md

Freeze ./integration and explain where to contribute new tests

2014-04-26 18:55:39 -07:00

runtime_test.go

Move CLI config processing out from under registry dir

2015-04-23 10:18:38 -07:00

utils_test.go

Remove builtins

2015-04-17 14:27:38 +02:00

utils.go

remove integration/utils setRaw funcs

2015-04-14 15:17:17 -04:00

z_final_test.go

Refactor utils/utils, fixes #11923

2015-04-14 01:37:36 +02:00

README.md

Legacy integration tests

./integration contains Docker's legacy integration tests. It is DEPRECATED and will eventually be removed.

If you are a CONTRIBUTOR and want to add a test:

Consider mocking out side effects and contributing a unit test in the subsystem you're modifying. For example, the remote API has unit tests in ./api/server/server_unit_tests.go. The events subsystem has unit tests in ./events/events_test.go. And so on.
For end-to-end integration tests, please contribute to ./integration-cli.

If you are a MAINTAINER

Please don't allow patches adding new tests to ./integration.

If you are LOOKING FOR A WAY TO HELP

Please consider porting tests away from ./integration and into either unit tests or CLI tests.

Any help will be greatly appreciated!