You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: migrate e2e presubmit tests to bigframes-load-testing project (#160)
BEGIN_COMMIT_OVERRIDE
fix: migrate e2e tests to bigframes-load-testing project
END_COMMIT_OVERRIDE
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
- [ ] Make sure to open an issue as a [bug/issue](https://togithub.com/googleapis/python-bigquery-dataframes/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
- [ ] Ensure the tests and linter pass
- [ ] Code coverage does not decrease (if any source code was changed)
- [ ] Appropriate docs were updated (if necessary)
Fixes internal issue 307809767 🦕
Copy file name to clipboardExpand all lines: CONTRIBUTING.rst
+38-1Lines changed: 38 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -155,7 +155,44 @@ Running System Tests
155
155
auth settings and change some configuration in your project to
156
156
run all the tests.
157
157
158
-
- System tests will be run against an actual project. You should use local credentials from gcloud when possible. See `Best practices for application authentication <https://cloud.google.com/docs/authentication/best-practices-applications#local_development_and_testing_with_the>`__. Some tests require a service account. For those tests see `Authenticating as a service account <https://cloud.google.com/docs/authentication/production>`__.
158
+
- System tests will be run against an actual project. A project can be set in
159
+
the environment variable ``$GOOGLE_CLOUD_PROJECT``. If not, the project property
160
+
set in the `Google Cloud CLI <https://cloud.google.com/sdk/gcloud/reference/config/get>`__
161
+
will be effective, which can be peeked into via ``gcloud config get project``,
162
+
or set via ``gcloud config set project <project-name>``. The following roles
163
+
carry the permissions to run the system tests in the project:
164
+
165
+
- `BigQuery User <https://cloud.google.com/bigquery/docs/access-control#bigquery.user>`__
166
+
to be able to create test datasets and run BigQuery jobs in the project.
to be able to create cloud functions to support BigQuery DataFrames remote functions.
179
+
180
+
- `Service Account User <https://cloud.google.com/iam/docs/service-account-permissions#user-role>`__
181
+
to be able to use the project's service accounts.
182
+
183
+
- `Vertex AI User <https://cloud.google.com/vertex-ai/docs/general/access-control#aiplatform.user>`__
184
+
to be able to use the BigQuery DataFrames' ML integration with Vertex AI.
185
+
186
+
- You can run the script ``scripts/setup-project-for-testing.sh <project-id> [<principal>]``
187
+
to set up a project for running system tests and optionally set up necessary
188
+
IAM roles for a principal (user/group/service-account). You need to have the following
189
+
IAM permission to be able to run the set up script successfully:
190
+
191
+
- ``serviceusage.services.enable``
192
+
- ``bigquery.connections.create``
193
+
- ``resourcemanager.projects.setIamPolicy``
194
+
195
+
- You should use local credentials from gcloud when possible. See `Best practices for application authentication <https://cloud.google.com/docs/authentication/best-practices-applications#local_development_and_testing_with_the>`__. Some tests require a service account. For those tests see `Authenticating as a service account <https://cloud.google.com/docs/authentication/production>`__.
0 commit comments