Integration Test Failure Caused by Database Rules

[hiranya911]

Integration test suite may sometimes fail with the following error:

FIREBASE WARNING: set at /blocked failed: permission_denied 
[FAILURE] nonNullApp.database().ref("blocked").set(): Error: PERMISSION_DENIED: Permission denied

This happens when there are custom rules in the realtime database. Changing the rules back to defaults usually fixes the issue:

{
  "rules": {
    ".read": "auth != null",
    ".write": "auth != null",
  }
}

The integration test suite should not depend on a specific rules configuration. If such a dependency is needed, the test suite should update the rules config during the setup phase (Java and Python SDKs do this already).

[hiranya911]

This has been implemented. Integration tests overwrite the database rules with the defaults now. If this is deemed too invasive, we can implement a warning+prompt mechanism in the future.