Testing rules with emulator in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of using an emulator when testing Firebase security rules?

An emulator lets you test your Firebase security rules locally without affecting real data or users. It helps catch mistakes safely before deploying.

beginner

How do Firebase emulators help in the development process?

They provide a safe environment to simulate database, authentication, and other Firebase services, allowing quick testing and debugging of rules and code.

beginner

Which Firebase CLI command starts the local emulator for testing rules?

The command is firebase emulators:start. It launches the configured emulators for your project.

intermediate

Why should you test security rules with different user authentication states in the emulator?

Because rules often depend on whether a user is signed in or their role. Testing different states ensures rules work correctly for all cases.

intermediate

What is a key benefit of using the Firebase emulator suite over testing rules directly in production?

It prevents accidental data loss or exposure by isolating tests from live data and users, making testing safe and repeatable.

What does the Firebase emulator suite allow you to do?

A Automatically fix rule errors

B Deploy rules directly to production

C Test security rules locally without affecting live data

D Replace Firebase hosting

The emulator suite lets you test rules locally safely without changing real data.

Which command starts the Firebase emulators?

A firebase deploy

B firebase serve

C firebase init

D firebase emulators:start

firebase emulators:start launches the local emulators.

Why test rules with different user sign-in states in the emulator?

A To check UI design

B To verify rules handle permissions correctly

C To speed up deployment

D To backup data

Rules often depend on user authentication, so testing different states ensures correct permissions.

What is NOT a feature of the Firebase emulator suite?

A Automatically deploy to production

B Test Authentication flows

C Simulate Firestore database

D Run Cloud Functions locally

The emulator does not deploy to production; it only simulates services locally.

What is a main advantage of using emulators for rule testing?

A Safe testing without risking live data

B Faster internet connection

C Free cloud storage

D Automatic code generation

Emulators allow safe testing without affecting live data or users.

Explain how the Firebase emulator suite helps in testing security rules before deployment.

Think about why testing locally is safer and faster.

Describe the steps to start testing Firebase security rules using the emulator.

Focus on setup and running the emulator.

Practice

1. What is the main purpose of using the Firebase emulator when testing Firestore security rules?

easy

A. To safely test rules without affecting live data

B. To deploy rules directly to production

C. To speed up Firestore queries in production

D. To backup Firestore data automatically

Solution

1. Step 1: Understand the role of the emulator

   The Firebase emulator creates a safe environment that mimics Firestore without touching live data.

2. Step 2: Identify the benefit of safe testing

   This allows developers to test security rules without risking data loss or exposure in production.

3. Final Answer:

   To safely test rules without affecting live data -> Option A

4. Quick Check:

   Emulator = Safe testing environment [OK]

Hint: Emulator means safe testing, no live data risk [OK]

Common Mistakes:

• Thinking emulator deploys rules to production
• Confusing emulator with data backup tool
• Assuming emulator speeds up production queries

2. Which command correctly starts only the Firestore emulator?

easy

A. firebase start firestore

B. firebase emulators:start --only firestore

C. firebase emulators:run firestore

D. firebase firestore:start

Solution

1. Step 1: Recall the correct Firebase CLI command

   The command to start emulators selectively uses 'firebase emulators:start --only' followed by the service name.

2. Step 2: Match the command to Firestore emulator

   For Firestore only, the command is 'firebase emulators:start --only firestore'.

3. Final Answer:

   firebase emulators:start --only firestore -> Option B

4. Quick Check:

   Correct CLI syntax = firebase emulators:start --only firestore [OK]

Hint: Use --only with service name to start specific emulator [OK]

Common Mistakes:

• Using 'firebase start firestore' which is invalid
• Confusing 'run' with 'start' in command
• Omitting '--only' flag

3. Given this Firestore security rule snippet tested in the emulator:

service cloud.firestore {
  match /databases/{database}/documents {
    match /messages/{msgId} {
      allow read: if request.auth != null;
      allow write: if false;
    }
  }
}

What will happen if an unauthenticated user tries to read a message?

medium

A. Read is denied

B. Write is allowed

C. Read is allowed

D. Write is denied

Solution

1. Step 1: Analyze the read rule condition

   The rule allows read only if request.auth is not null, meaning user must be authenticated.

2. Step 2: Check the user's authentication status

   The user is unauthenticated, so request.auth is null, failing the condition.

3. Final Answer:

   Read is denied -> Option A

4. Quick Check:

   Unauthenticated read = denied [OK]

Hint: Read allowed only if user is authenticated [OK]

Common Mistakes:

• Assuming read is allowed without authentication
• Confusing read and write permissions
• Ignoring the request.auth check

4. You wrote this rule in the emulator but all writes are failing:

allow write: if request.auth.uid == userId;

What is the likely error causing the failure?

medium

A. request.auth.uid is always null in emulator

B. Emulator does not support write rules

C. Write rules cannot use '==' operator

D. The variable 'userId' is not defined in the rule context

Solution

1. Step 1: Check the rule variable usage

   The rule compares request.auth.uid to userId, but userId is not defined or extracted from the document path or data.

2. Step 2: Understand rule variable scope

   Variables like userId must be defined in the path or request data; otherwise, the condition fails.

3. Final Answer:

   The variable 'userId' is not defined in the rule context -> Option D

4. Quick Check:

   Undefined variable causes rule failure [OK]

Hint: Ensure all variables in rules are properly defined [OK]

Common Mistakes:

• Assuming emulator nullifies request.auth.uid
• Thinking '==' is invalid in rules
• Believing emulator ignores write rules

5. You want to test that only users can write their own profile document in the emulator. The document path is /users/{userId}. Which rule correctly enforces this and can be tested in the emulator?

hard

A. allow write: if true;

B. allow write: if request.auth.uid != userId;

C. allow write: if request.auth.uid == userId;

D. allow write: if request.auth != null;

Solution

1. Step 1: Match userId from document path

   In rules, userId is a variable from the path /users/{userId} and can be used in conditions.

2. Step 2: Enforce write only if authenticated user matches userId

   The condition 'request.auth.uid == userId' ensures only the user can write their own profile.

3. Final Answer:

   allow write: if request.auth.uid == userId; -> Option C

4. Quick Check:

   User writes own doc = request.auth.uid == userId [OK]

Hint: Match auth uid to path userId for user-specific writes [OK]

Common Mistakes:

• Using '!=' instead of '==' causing wrong access
• Allowing any authenticated user to write all profiles
• Setting rule to always true, no security