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
One notable change made here is that we generate and include ID tokens in requests to http/callable functions since we aren't allowed to run public functions on internal GCP project.
Copy file name to clipboardExpand all lines: integration_test/README.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,15 @@ Run the integration test as follows:
8
8
./run_tests.sh <project_id> [<project_id2>]
9
9
```
10
10
11
-
If just one project_id is provided, the both the node6 and node8 tests will be run on that project, in series. If two project_ids are provided, the node6 tests will be run on the first project and the node8 tests will be run on the second one, in parallel.
11
+
Test runs cycles of testing, once for Node.js 14 and another for Node.js 16.
12
12
13
-
The tests run fully automatically, and will print the result on standard out. The integration test for HTTPS is that it properly kicks off other integration tests and returns a result. From there the other integration test suites will write their results back to the database, where you can check the detailed results if you'd like.
13
+
Test uses locally installed firebase to invoke commands for deploying function. The test also requires that you have
14
+
gcloud CLI installed and authenticated (`gcloud auth login`).
15
+
16
+
Integration test is triggered by invoking HTTP function integrationTest which in turns invokes each function trigger
17
+
by issuing actions necessary to trigger it (e.g. write to storage bucket).
18
+
19
+
### Debugging
20
+
21
+
The status and result of each test is stored in RTDB of the project used for testing. You can also inspect Cloud Logging
0 commit comments