p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
f0bbbffba07fa21ce34ca8792bd44dcc55896542
docker-cli/components/engine/integration
History
Alexander Morozov 79e92cb2ff Merge pull request #12567 from brahmaroutu/integration_test6_12255 
moving integration tests to graph unit tests
Upstream-commit: 7ba8c3b26ffedc869c2868c3e90ef81315af6b8f
Component: engine
2015-04-21 13:58:02 -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
Make all http handlers api.server.Server methods
2015-04-20 09:45:31 -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!