3

I want to run some browser tests against my Firebase/Firestore application. They will be running in CI, so I want them to run in separate environments that won't collide with each other.

If I were writing my own backend, this would be easy: I would just run a local backend and database. However, this isn't possible yet with Firebase and Firestore.

A possible solution would be to programmatically create Firebase projects for each test run, but this doesn't seem to be possible. Similarly, each test could run in its own namespace, but this also doesn't seem to be possible.

What is the best practice for creating test environments for Firebase/Firestore apps?

bfirsh
  • 63
  • 3
  • Do you tests need to run in parallel such that you need to programmatically create a project each one? If not, just dedicate a single project for tests and reset it before each test run. – Doug Stevenson Jun 07 '18 at 16:36

2 Answers2

1

UPDATE: The Firebase team has recently released the Firebase Management API:

The Firebase Management API enables programmatic setup and management of Firebase projects, including a project's Firebase resources and Firebase apps.

I have not had a chance to test it out but in theory it would be ideal for setting up and disposing of environments programmatically on demand as part of a any CI/CD setup.

ra9r
  • 4,528
  • 4
  • 42
  • 52
0

I would recommend creating a separate firebase project with the same settings as your live project and run your tests there. I have does this and it works well. This solution gives you the ability to have test data in Firestone which is separate from live/production.

Peter Fields
  • 389
  • 1
  • 3
  • 9
  • 2
    Unfortunately that won't work if two tests need to run in parallel. This technique will sort of work if you can write tests that won't collide with another set of running tests (e.g. with random names), but it completely falls apart if you want to test some new security rules or cloud functions. – bfirsh Jun 09 '18 at 09:42