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(storage): add support for Storage TestBench (#210)
The Google Cloud Storage team provides a project called "Storage
Testbench" that is used for failure testing in Google Cloud Storage
clients. Storage Testbench can be run using docker and provides a
partial GCS implementation that can be scripted to produce failures.
This PR adds the ability to create tests that target Storage Testbench
and a trivial test to prove that it works.
- Creates a new test tag `storage-testbench`
- Adds a new GitHub workflow that starts the docker image and runs tests
with that tag
- Adds test utilities to work with Storage Testbench
- Documents how to run Storage Testbench locally
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Nate Bosch <nbosch1@gmail.com>
Copy file name to clipboardExpand all lines: DEVELOPER_GUIDE.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,27 @@ To run these tests locally (they are automatically run for PRs using
59
59
***Missing Scopes:** If a test fails with `insufficient_scope`, check the error message for the required scope URL and re-authenticate with that scope.
60
60
***Disabled APIs:** If a test fails with a `ForbiddenException` stating an API has not been used, follow the URL in the error message to enable the API in the Google Cloud Console.
61
61
62
+
### Running against Storage Testbench
63
+
64
+
Some integration tests in`package:google_cloud_storage` use the
65
+
[Storage Testbench][]. These tests are tagged with
66
+
`@Tags(['storage-testbench'])` and are not run by default, i.e., `dart test`
67
+
will not run them.
68
+
69
+
To run these tests locally (they are automatically run for PRs using a
0 commit comments