summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-merge-robot <k8s.production.user@gmail.com>2016-02-01 10:29:15 -0800
committerk8s-merge-robot <k8s.production.user@gmail.com>2016-02-01 10:29:15 -0800
commitf4e276aaad176f57e398504b2aec9b1965407057 (patch)
tree592d5715a6ab2731caff9a2c4a77d49a0305e5f1
parentee65341b8a41d7eee2b285691482b9592f14febf (diff)
parentd37c7d1df600ba12d7205f32685724cc4abb88b4 (diff)
Merge pull request #20315 from pmorie/e2e-doc
Auto commit by PR queue bot
-rw-r--r--coding-conventions.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/coding-conventions.md b/coding-conventions.md
index e0a1e146..6af7c40e 100644
--- a/coding-conventions.md
+++ b/coding-conventions.md
@@ -61,7 +61,7 @@ Code conventions
Testing conventions
- All new packages and most new significant functionality must come with unit tests
- Table-driven tests are preferred for testing multiple scenarios/inputs; for example, see [TestNamespaceAuthorization](../../test/integration/auth_test.go)
- - Significant features should come with integration (test/integration) and/or end-to-end (test/e2e) tests
+ - Significant features should come with integration (test/integration) and/or [end-to-end (test/e2e) tests](e2e-tests.md)
- Including new kubectl commands and major features of existing commands
- Unit tests must pass on OS X and Windows platforms - if you use Linux specific features, your test case must either be skipped on windows or compiled out (skipped is better when running Linux specific commands, compiled out is required when your code does not compile on Windows).