diff options
| author | jayunit100 <jay@apache.org> | 2016-09-20 11:23:00 -0400 |
|---|---|---|
| committer | jayunit100 <jay@apache.org> | 2016-09-20 15:42:22 -0400 |
| commit | eb797e756de41791fcba07ef874ebf8673671b7d (patch) | |
| tree | 37da91003c390be0959b7f8925779be94a04ea62 | |
| parent | 19d5af9961ab07c650aeabfd0e65a8a73e7fd893 (diff) | |
viper hierarchies, cadvisor impl
| -rw-r--r-- | e2e-tests.md | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/e2e-tests.md b/e2e-tests.md index b0d0860d..6d457f59 100644 --- a/e2e-tests.md +++ b/e2e-tests.md @@ -58,6 +58,7 @@ Updated: 5/3/2016 - [Testing against local clusters](#testing-against-local-clusters) - [Version-skewed and upgrade testing](#version-skewed-and-upgrade-testing) - [Kinds of tests](#kinds-of-tests) + - [Viper configuration and hierarchichal test parameters.](#viper-configuration-and-hierarchichal-test-parameters) - [Conformance tests](#conformance-tests) - [Defining Conformance Subset](#defining-conformance-subset) - [Continuous Integration](#continuous-integration) @@ -511,6 +512,20 @@ breaking changes, it does *not* block the merge-queue, and thus should run in some separate test suites owned by the feature owner(s) (see [Continuous Integration](#continuous-integration) below). +### Viper configuration and hierarchichal test parameters. + +The future of e2e test configuration idioms will be increasingly defined using viper, and decreasingly via flags. + +Flags in general fall apart once tests become sufficiently complicated. So, even if we could use another flag library, it wouldn't be ideal. + +To use viper, rather than flags, to configure your tests: + +- Just add "e2e.json" to the current directory you are in, and define parameters in it... i.e. `"kubeconfig":"/tmp/x"`. + +Note that advanced testing parameters, and hierarchichally defined parameters, are only defined in viper, to see what they are, you can dive into [TestContextType](../../test/e2e/framework/test_context.go). + +In time, it is our intent to add or autogenerate a sample viper configuration that includes all e2e parameters, to ship with kubernetes. + ### Conformance tests Finally, `[Conformance]` tests represent a subset of the e2e-tests we expect to |