Testing rules with emulator in Firebase - Step-by-Step Execution

Process Flow - Testing rules with emulator

Start Emulator

↓

Load Security Rules

↓

Run Test Requests

↓

Check Request Outcome

↓

Log Success

↓

Stop Emulator

This flow shows starting the emulator, loading rules, running test requests, checking if they pass or fail, logging results, and stopping the emulator.

Execution Sample

Firebase

firebase emulators:exec --only firestore "npm test"
# Test read and write permissions

Starts the Firestore emulator, runs security rule tests, and checks if read/write requests are allowed or denied.

Process Table

Step	Action	Request Type	Rule Check Result	Outcome
1	Start Firestore Emulator	-	-	Emulator running
2	Load Security Rules	-	-	Rules loaded successfully
3	Test Read Request	Read	Allowed by rules	Pass
4	Test Write Request	Write	Denied by rules	Fail
5	Log Results	-	-	Read: Pass, Write: Fail
6	Stop Emulator	-	-	Emulator stopped

💡 All test requests processed; emulator stopped.

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
Emulator Status	Stopped	Running	Running	Stopped
Rules Loaded	No	Yes	Yes	Yes
Read Request Result	N/A	Allowed	Allowed	Allowed
Write Request Result	N/A	N/A	Denied	Denied
Test Outcome	N/A	Pass	Fail	Fail

Key Moments - 2 Insights

Why does the write request fail while the read request passes?

Because the security rules allow reads but deny writes, as shown in execution_table rows 3 and 4.

What happens if the emulator is not started before testing?

The tests cannot run because the emulator must be running to simulate requests, as shown in step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the outcome of the write request test at step 4?

A Fail

B Skipped

C Pass

D Error

💡 Hint

Check the 'Outcome' column at step 4 in the execution_table.

At which step does the emulator stop running?

A Step 3

B Step 5

C Step 6

D Step 2

💡 Hint

Look at the 'Action' and 'Emulator Status' variable in step 6.

If the security rules allowed writes, how would the 'Test Outcome' variable change after step 4?

A It would remain 'Fail'

B It would change to 'Pass'

C It would be 'Error'

D It would be 'Skipped'

💡 Hint

Refer to variable_tracker 'Test Outcome' after step 4 and consider rule changes.

Concept Snapshot

Testing rules with emulator:
- Start emulator to simulate your database.
- Load your security rules into emulator.
- Run test requests (read/write).
- Check if requests pass or fail based on rules.
- Stop emulator after tests.

Full Transcript

To test Firebase security rules, first start the emulator to simulate your database environment. Then load your security rules into the emulator. Next, run test requests such as reads and writes to see if they are allowed or denied by your rules. Observe the results: if a request is allowed, it passes; if denied, it fails. Finally, stop the emulator to end the testing session. This process helps ensure your rules work as expected before deploying.