Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support running kubectl commands as a part of test harness #368

Closed
jbarrick-mesosphere opened this issue Jun 20, 2019 · 1 comment · Fixed by #656
Closed

Support running kubectl commands as a part of test harness #368

jbarrick-mesosphere opened this issue Jun 20, 2019 · 1 comment · Fixed by #656
Labels
component/testing kep/8 KEP Framework Testing kind/enhancement

Comments

@jbarrick-mesosphere
Copy link
Member

What would you like to be added:

Support running kubectl commands as a first class citizen in the test harness, along side the declarative tests.

Why is this needed:

Discussing the test harness with @fabianbaier it seems that there are some cases where it would be useful to be able to test a kubectl command as a part of a test:

  • Increase test coverage to include CLI commands.
  • Simplify writing some tests.
@jbarrick-mesosphere
Copy link
Member Author

IMO we shouldn't implement this one right away - rather, wait for a compelling use-case to come up.

jbarrick-mesosphere added a commit to jbarrick-mesosphere/kudo that referenced this issue Jul 23, 2019
@jbarrick-mesosphere
Implement CLI and E2E testing using the KUDO test harness.
0d13d9f 
Fixes kudobuilder#368 (support CLI commands)
Fixes kudobuilder#369 (support install kudo frameworks)
Fixes kudobuilder#520 (panic when executing test harness)

This adds a `kubectl` setting to the KUDO test harness TestSuite and TestStep configurations to support running kubectl commands
as a part of tests.
jbarrick-mesosphere added a commit to jbarrick-mesosphere/kudo that referenced this issue Jul 26, 2019
@jbarrick-mesosphere
Implement CLI and E2E testing using the KUDO test harness.
6ff97d0 
Fixes kudobuilder#368 (support CLI commands)
Fixes kudobuilder#369 (support install kudo frameworks)
Fixes kudobuilder#520 (panic when executing test harness)

This adds a `kubectl` setting to the KUDO test harness TestSuite and TestStep configurations to support running kubectl commands
as a part of tests.
@jbarrick-mesosphere jbarrick-mesosphere mentioned this issue Jul 26, 2019
Merged
jbarrick-mesosphere added a commit to jbarrick-mesosphere/kudo that referenced this issue Jul 26, 2019
@jbarrick-mesosphere
Implement CLI and E2E testing using the KUDO test harness.
445d3d1 
Fixes kudobuilder#368 (support CLI commands)
Fixes kudobuilder#369 (support install kudo frameworks)
Fixes kudobuilder#520 (panic when executing test harness)

This adds a `kubectl` setting to the KUDO test harness TestSuite and TestStep configurations to support running kubectl commands
as a part of tests.
jbarrick-mesosphere added a commit to jbarrick-mesosphere/kudo that referenced this issue Jul 29, 2019
@jbarrick-mesosphere
Implement CLI and E2E testing using the KUDO test harness.
e58ba10 
Fixes kudobuilder#368 (support CLI commands)
Fixes kudobuilder#369 (support install kudo frameworks)
Fixes kudobuilder#520 (panic when executing test harness)

This adds a `kubectl` setting to the KUDO test harness TestSuite and TestStep configurations to support running kubectl commands
as a part of tests.
jbarrick-mesosphere added a commit that referenced this issue Jul 31, 2019
@jbarrick-mesosphere
Implement CLI and E2E testing using the KUDO test harness. (#656)
3f45ece 
* Implement CLI and E2E testing using the KUDO test harness.

Fixes #368 (support CLI commands)
Fixes #369 (support install kudo frameworks)
Fixes #520 (panic when executing test harness)

This adds a `kubectl` setting to the KUDO test harness TestSuite and TestStep configurations to support running kubectl commands
as a part of tests.

* Log files that are ignored by test harness.

* factor DoKubectl -> testutils.RunKubectlCommands

* Clean up kubectl argument parsing.

* Fix broken logging and log stderr instead of writing it to an error.

* make cli-test -> make cli-fast

* make cli-test -> make cli-fast
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/testing kep/8 KEP Framework Testing kind/enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement CLI and E2E testing using the KUDO test harness. jbarrick-mesosphere/kudo
1 participant
@jbarrick-mesosphere