From 41587e2810a1ba1f499c4dbcb4373442c1399e3d Mon Sep 17 00:00:00 2001 From: Paul Morie Date: Sat, 30 Jan 2016 00:06:34 -0500 Subject: [PATCH] Add link to e2e docs from coding conventions --- docs/devel/coding-conventions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/devel/coding-conventions.md b/docs/devel/coding-conventions.md index e0a1e1467f7..6af7c40e0b3 100644 --- a/docs/devel/coding-conventions.md +++ b/docs/devel/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).