docker/integration
Arnaud Porterie 89bdaa35e0 Remove subdirectories MAINTAINERS files
Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>
2015-03-06 18:21:51 -08:00
..
fixtures/https Add authenticated TLS support for API 2014-03-09 00:06:44 +01:00
README.md Freeze ./integration and explain where to contribute new tests 2014-04-26 18:55:39 -07:00
api_test.go instantiate the builder job in commit integration tests 2015-02-24 13:01:35 -05:00
commands_test.go Removing dependencies from pkg into Docker internal code 2015-02-23 18:43:10 +00:00
container_test.go Rename Destroy to Rm to be consistent with CLI. 2015-02-23 16:15:56 +01:00
graph_test.go Removing dependencies from pkg into Docker internal code 2015-02-23 18:43:10 +00:00
https_test.go Defer creation of trust key file until needed 2015-01-29 13:46:12 -08:00
runtime_test.go Removing dependencies from pkg into Docker internal code 2015-02-23 18:43:10 +00:00
server_test.go instantiate the builder job in commit integration tests 2015-02-24 13:01:35 -05:00
utils_test.go Rename Destroy to Rm to be consistent with CLI. 2015-02-23 16:15:56 +01: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!