beenull/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
moby/integration
History
David Calavera 002afbbe77 Make integration tests to call the new start and create endpoints. 
Signed-off-by: David Calavera <david.calavera@gmail.com>
2015-04-14 15:33:33 -07:00
..
fixtures/https Revert "Dealing with trailing whitespaces" 2015-03-25 10:04:56 -06:00
api_test.go Link to HTTPS URLs in engine comments 2015-04-11 13:31:34 -04:00
container_test.go Rename Destroy to Rm to be consistent with CLI. 2015-02-23 16:15:56 +01:00
graph_test.go Refactor utils/utils, fixes #11923 2015-04-14 01:37:36 +02: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 integration tests to call the new start and create endpoints. 2015-04-14 15:33:33 -07:00
utils.go remove integration/utils setRaw funcs 2015-04-14 15:17:17 -04:00
utils_test.go Make integration tests to call the new start and create endpoints. 2015-04-14 15:33:33 -07: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!