-
Notifications
You must be signed in to change notification settings - Fork 159
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
Improve upgrade test coverage #2855
Conversation
Does the PR have any schema changes?Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
Looks like there's a problem here that tests under provider/* are not being run. |
Fixes #661 The reason I'm working on this now is that I'd like to really move upgrade tests out of examples and under provider/ in AWS (and soon GCP). pulumi/pulumi-aws#2855
54da24d
to
32ba400
Compare
Codecov Report
@@ Coverage Diff @@
## master #2855 +/- ##
==============================
==============================
📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today! |
I'm confused why https://github.com/pulumi/pulumi-aws/actions/runs/6830265431/job/18578614635#step:24:209 invocation is not running the new tests seemingly. The command is:
Locally I see this running the new tests. |
Looks like we got past spurious test failures by force-cleaning the test AWS account. |
func TestBucket(t *testing.T) { | ||
test(t, filepath.Join("test-programs", "bucket")) | ||
} | ||
|
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.
I'm curious why you switched to making a separate test function for each program rather than just iterating the test directory and generating one per program.
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.
I believe I'm taking style guidance from @danielrbradley on this; both are idiomatic Go as far as I can tell. This style is even easier to point-and-click running a test in VS Code.
Increase upgrade test coverage. Fixes https://github.com/pulumi/home/issues/3130