@@ -127,23 +127,10 @@ mvn test
127
127
Integration tests are also written using Junit4. They coexist with the unit tests in the ` src/test `
128
128
subdirectory. Integration tests follow the naming convention ` *IT.java ` (e.g. ` DataTestIT.java ` ),
129
129
which enables the Maven Surefire and Failsafe plugins to differentiate between the two types of
130
- tests. Integration tests are executed against a real life Firebase project, and therefore
131
- requires an Internet connection.
132
-
133
- Create a new project in the [ Firebase console] ( https://console.firebase.google.com/ ) if you do
134
- not already have one. Use a separate, dedicated project for integration tests since the test suite
135
- makes a large number of writes to the Firebase realtime database. Download the service account
136
- private key from the "Settings > Service Accounts" page of the project, and save it as
137
- ` integration_cert.json ` at the root of the codebase. Grant your service account the `Firebase
138
- Authentication Admin` role at
139
- [ Google Cloud Platform Console / IAM & admin] ( https://console.cloud.google.com/iam-admin ) . This is
140
- required to ensure that exported user records contain the password hashes of the user accounts.
141
- Also obtain the web API key of the project from the "Settings > General" page, and save it as
142
- ` integration_apikey.txt ` at the root of the codebase.
143
-
144
-
145
- If you do not already have one suitable for running the tests against, you can create a new
146
- project in the
130
+ tests.
131
+
132
+ Integration tests are executed against a real life Firebase project. If you do not already
133
+ have one suitable for running the tests against, you can create a new project in the
147
134
[ Firebase Console] ( https://console.firebase.google.com ) following the setup guide below.
148
135
Otherwise you can obtain the following credentials from your current project:
149
136
0 commit comments