docker-cli

Files

Oh Jinkyun 18373aa635 Removed runconfig.ParseSubcommand

Removed runconfig.ParseSubcommand, changed it to runconfig.Parse and editted related tests and modules

Signed-off-by: Oh Jinkyun <tintypemolly@gmail.com>
Upstream-commit: 9aa71549d61875fcf0713a9da11b034e70e1c3b0
Component: engine

2014-09-17 14:38:22 -07:00

fixtures/https

Add authenticated TLS support for API

2014-03-09 00:06:44 +01:00

api_test.go

update go import path and libcontainer

2014-07-24 22:19:50 +00:00

commands_test.go

Use State as embedded to Container

2014-09-03 00:01:11 +04:00

container_test.go

Use State as embedded to Container

2014-09-03 00:01:11 +04:00

graph_test.go

graph: change argument order of Register function

2014-08-28 20:06:07 +09:00

https_test.go

update go import path and libcontainer

2014-07-24 22:19:50 +00:00

MAINTAINERS

Add Cristian to integration/MAINTAINERS

2014-08-13 07:50:40 +00:00

README.md

Freeze ./integration and explain where to contribute new tests

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

runtime_test.go

Removed runconfig.ParseSubcommand

2014-09-17 14:38:22 -07:00

server_test.go

Removed runconfig.ParseSubcommand

2014-09-17 14:38:22 -07:00

utils_test.go

Removed runconfig.ParseSubcommand

2014-09-17 14:38:22 -07:00

z_final_test.go

update go import path and libcontainer

2014-07-24 22:19:50 +00: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!