Commit Graph

7 Commits

Author SHA1 Message Date
Kenichi Omichi
9e9c1709db Use log functions of core framework on sub p*
This makes sub packages of e2e test framework to use log functions
of core framework instead for avoiding circular dependencies.

NOTE: subpackage pod would make circular dependency if changing here.
      So we need to take care of it with another PR.
2019-08-23 19:50:47 +00:00
SataQiu
c60377c682 fix static check for test/e2e/framework 2019-08-21 17:28:36 +08:00
SataQiu
d3a902ff5b e2e refactor: cleanup Logf form framework/util 2019-05-24 16:39:46 +08:00
Mike Crute
6f5cf1a6e0 Staging legacy AWS cloud provider 2019-05-06 09:34:13 -07:00
Kenichi Omichi
36b80a4c61 Fix golint failures on e2e/[..]/(aws|azure) 2019-02-20 19:11:53 +00:00
andrewsykim
596c6fbf03 e2e test for node deleted in cloud provider 2019-01-25 17:45:18 -05:00
Patrick Ohly
8b17db7e0c e2e: modular framework
Not all users of the E2E framework want to run cloud-provider specific
tests. By splitting out the code it becomes possible to decide in
a E2E test suite which providers are supported.

This is achieved in two ways:
- the framework calls certain functions through a provider
  interface instead of calling specific cloud provider functions
  directly
- tests that are cloud-provider specific directly import the
  new provider packages

The ingress test utilities are only needed by a few tests. Splitting
them out into a separate package makes the framework simpler for test
suites not using those tests.

Fixes: #66649
2018-10-11 11:16:11 +02:00