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
Tests against real (GCP production) Firestore will presumably be more accurate wrt to transactions, indices, and security rules.
To do this properly we will need to:
Create a test GCP project to separate prod and test environments.
Be able to set the GCP project with a flag or environment variable, and set it from the GitHub actions
Namespace all collections so that tests can run in parallel without interfering with each other. The root collection somewhat obviously needs to namespaces, but so do any collections that are used in a .collectionGroup() query, like customElements, so it's probably best to just make factories for all Firestore references and namespace them all.
Have a robust data cleanup script that runs after tests. This script will need to use the namespace used in the tests it's cleaning up after.
The text was updated successfully, but these errors were encountered:
Tests against real (GCP production) Firestore will presumably be more accurate wrt to transactions, indices, and security rules.
To do this properly we will need to:
.collectionGroup()
query, likecustomElements
, so it's probably best to just make factories for all Firestore references and namespace them all.The text was updated successfully, but these errors were encountered: