Denver Coneybeare 95add7fc85 Fix documentation warning surfaced in Xcode from grpc (#6354) 5 jaren geleden
..
Example 73fcb194d8 Add conditional conformance to Hashable to Firestore property wrapper types (#6249) 5 jaren geleden
Protos f33276f530 Update nanopb py3 0.3.9.5 -> 0.3.9.6 (#6214) 5 jaren geleden
Source 160f21a6ca Make the language reported via headers configurable (#6264) 5 jaren geleden
Swift 73fcb194d8 Add conditional conformance to Hashable to Firestore property wrapper types (#6249) 5 jaren geleden
core 95add7fc85 Fix documentation warning surfaced in Xcode from grpc (#6354) 5 jaren geleden
fuzzing 7a58eba2e5 Remove `firebase/firestore` from paths in Firestore/core (#5374) 6 jaren geleden
third_party eabe8d46a0 Update and apply swiftformat fix (#6239) 5 jaren geleden
CHANGELOG.md 0d729f1b8f Update CHANGELOG for Firestore v1.17.0 (#6299) 5 jaren geleden
CMakeLists.txt 2a8d069b77 Run integration tests from CMake on mac (#4276) 6 jaren geleden
README.md 2656033eb2 Update integration testing docs (#5490) 6 jaren geleden
test.sh 5930ad2fee Factor out a universal build script (#884) 8 jaren geleden

README.md

Usage

  • Install prerequisite software
  • Set up a workspace via CocoaPods

    $ cd Firestore/Example
    $ pod update
    $ open Firestore.xcworkspace
    
  • Select the Firestore_Tests_iOS scheme

  • ⌘-u to build and run the unit tests

Improving the debugger experience

You can install a set of type formatters to improve the presentation of Firestore internals in LLDB and Xcode. Add the following to your ~/.lldbinit file:

command script import ~/path/to/firebase-ios-sdk/scripts/lldb/firestore.py

(substitute the location of your checkout of the firebase-ios-sdk.)

Running Integration Tests

Prefer running the integration tests against the Firestore Emulator. This is much faster than running against production and does not require you to configure a Firestore-enabled project.

  • In a new terminal, run scripts/run_firestore_emulator.sh and leave it running.
  • In Xcode select the Firestore_IntegrationTests_iOS scheme (or macOS or tvOS).
  • ⌘-u to build and run the integration tests.

Running Integration Tests - against production

Occasionally it's useful to run integration tests against a production account.

  • Set up a GoogleServices-Info.plist file in Firestore/Example/App.
  • Ensure your Firestore database has open rules (the integration tests do not authenticate).
  • In Xcode select the Firestore_IntegrationTests_iOS scheme
  • ⌘-u to build and run the integration tests

If you want to switch back to running integration tests against the emulator:

  • Ensure that GoogleServices-Info.plist is in its default state (git checkout Firestore/Example/App/GoogleServices-Info.plist).

Building Protos

Typically you should not need to worrying about regenerating the C++ files from the .proto files. If you do, see instructions at Protos/README.md.