-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Implement EC install CLI command integration test #1420
Implement EC install CLI command integration test #1420
Conversation
5399fc5
to
4235ad1
Compare
This PR has been released (on staging) and is available for download with a embedded-cluster-smoke-test-staging-app license ID. Online Installer:
Airgap Installer (may take a few minutes before the airgap bundle is built):
Happy debugging! |
tests/dryrun/util.go
Outdated
} | ||
} | ||
|
||
func assertMetrics(t *testing.T, actual []dryruntypes.Metric, expected map[string]func(string)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
expected maybe should be a slice so you can assert order
//go:embed assets/install-release.yaml | ||
var releaseData string | ||
|
||
func dryrunInstall(t *testing.T, args ...string) dryruntypes.DryRun { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be nice to export functions that are intended to be used in testing to make this package more self documenting including this, readK0sConfig, and the assert functions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is only intended to be used for dryrun tests though
e850f10
to
f7e31dc
Compare
f3e2f09
to
d73f4b3
Compare
What this PR does / why we need it:
Implements a framework for running CLI dry run tests.
Which issue(s) this PR fixes:
SC-114608
Does this PR require a test?
Yes
Does this PR require a release note?
Does this PR require documentation?
NONE
Example output