Julien P f6cbf82d59 Move mockpackage tests to closure integration tests (#15757) ... # Description The tests using `mockpackage` really should be integration tests. We worked around this by including `mockpackage` in our dependencies, but this has required some hackery in the build step to remove it again there. Now that we have the closure tests setup as integration tests, we can add the tests using mockpackage there. ## Checklist - [ ] I have run `make tidy` to update any new dependencies - [ ] I have run `make lint` to verify my code passes the lint check - [ ] I have formatted my code using `gofumpt` <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] I have added tests that prove my fix is effective or that my feature works <!--- User-facing changes require a CHANGELOG entry. --> - [ ] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Cloud, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> - [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version <!-- @Pulumi employees: If yes, you must submit corresponding changes in the service repo. -->		2024-03-26 11:38:01 +00:00
..
lib	Move mockpackage tests to closure integration tests (#15757)	2024-03-26 11:38:01 +00:00
package.json	Move mockpackage tests to closure integration tests (#15757)	2024-03-26 11:38:01 +00:00