diff options
| author | Tim St. Clair <stclair@google.com> | 2016-04-07 10:21:31 -0700 |
|---|---|---|
| committer | Tim St. Clair <stclair@google.com> | 2016-04-13 10:50:17 -0700 |
| commit | ff66c016355b4bd5ef92161e927426276913f025 (patch) | |
| tree | 0c999b227d1ef076b9f8d24759d84eca90d727f0 | |
| parent | a537b964a672d24df8cf973df4dfcf365798b757 (diff) | |
Update test/e2e for test/e2e/framework refactoring
| -rw-r--r-- | writing-good-e2e-tests.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/writing-good-e2e-tests.md b/writing-good-e2e-tests.md index 54b70030..2cb0fe47 100644 --- a/writing-good-e2e-tests.md +++ b/writing-good-e2e-tests.md @@ -180,7 +180,7 @@ right thing. Here are a few pointers: -+ [E2e Framework](../../test/e2e/framework.go): ++ [E2e Framework](../../test/e2e/framework/framework.go): Familiarise yourself with this test framework and how to use it. Amongst others, it automatically creates uniquely named namespaces within which your tests can run to avoid name clashes, and reliably @@ -194,7 +194,7 @@ Here are a few pointers: should always use this framework. Trying other home-grown approaches to avoiding name clashes and resource leaks has proven to be a very bad idea. -+ [E2e utils library](../../test/e2e/util.go): ++ [E2e utils library](../../test/e2e/framework/util.go): This handy library provides tons of reusable code for a host of commonly needed test functionality, including waiting for resources to enter specified states, safely and consistently retrying failed |