docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update test-and-docs.md (#2293) 

Add a missing space and delete extra spaces.
This commit is contained in:
Wang Jie 2017-03-14 17:02:07 +08:00 committed by John Mulhausen
parent d867751f2d
commit 15f1780cfb
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
opensource/project/test-and-docs.md
View File

@ -1,6 +1,6 @@
--- ---
description: Describes Docker's testing infrastructure description: Describes Docker's testing infrastructure
keywords: make test, make docs, Go tests, gofmt, contributing, running tests keywords: make test, make docs, Go tests, gofmt, contributing, running tests
title: Run tests and test documentation title: Run tests and test documentation
--- ---
@ -31,7 +31,7 @@ target="_blank">go test help</a>.
You are responsible for _unit testing_ your contribution when you add new or You are responsible for _unit testing_ your contribution when you add new or
change existing Docker code. A unit test is a piece of code that invokes a change existing Docker code. A unit test is a piece of code that invokes a
single, small piece of code ( _unit of work_ ) to verify the unit works as single, small piece of code (_unit of work_) to verify the unit works as
expected. expected.
Depending on your contribution, you may need to add _integration tests_. These Depending on your contribution, you may need to add _integration tests_. These
@ -48,7 +48,7 @@ change an existing one.
## Run tests on your local host ## Run tests on your local host
Before submitting a pull request with a code change, you should run the entire Before submitting a pull request with a code change, you should run the entire
Docker Engine test suite. The `Makefile` contains a target for the entire test Docker Engine test suite. The `Makefile` contains a target for the entire test
suite, named `test`. Also, it contains several targets for suite, named `test`. Also, it contains several targets for
testing: testing:
@ -91,7 +91,7 @@ hour. To run the test suite, do the following:
It can take approximate one hour to run all the tests. The time depends It can take approximate one hour to run all the tests. The time depends
on your host performance. The default timeout is 60 minutes, which is on your host performance. The default timeout is 60 minutes, which is
defined in `hack/make.sh`(`${TIMEOUT:=60m}`). You can modify the timeout defined in `hack/make.sh` (`${TIMEOUT:=60m}`). You can modify the timeout
value on the basis of your host performance. When they complete value on the basis of your host performance. When they complete
successfully, you see the output concludes with something like this: successfully, you see the output concludes with something like this:
@ -185,9 +185,9 @@ root@5f8630b873fe:/go/src/github.com/docker/docker# TESTFLAGS='-check.f TestBuil
## Test the Windows binary against a Linux daemon ## Test the Windows binary against a Linux daemon
This explains how to test the Windows binary on a Windows machine set up as a This explains how to test the Windows binary on a Windows machine set up as a
development environment. The tests will be run against a docker daemon development environment. The tests will be run against a docker daemon
running on a remote Linux machine. You'll use **Git Bash** that came with the running on a remote Linux machine. You'll use **Git Bash** that came with the
Git for Windows installation. **Git Bash**, just as it sounds, allows you to Git for Windows installation. **Git Bash**, just as it sounds, allows you to
run a Bash terminal on Windows. run a Bash terminal on Windows.
1. If you don't have one open already, start a Git Bash terminal. 1. If you don't have one open already, start a Git Bash terminal.