|
|
hace 5 años | |
|---|---|---|
| .. | ||
| Example | 24a77d04c8 Import Spec tests (#6525) | hace 5 años |
| Protos | 04b038eb21 add protos for != and NOT_IN (#6381) | hace 5 años |
| Source | 21921e9851 Add != and notIn support (#6418) | hace 5 años |
| Swift | 21921e9851 Add != and notIn support (#6418) | hace 5 años |
| core | 47fcf141ad Fix FSTGoogleTestTests under Xcode 12 (#6478) | hace 5 años |
| fuzzing | 7a58eba2e5 Remove `firebase/firestore` from paths in Firestore/core (#5374) | hace 6 años |
| third_party | eabe8d46a0 Update and apply swiftformat fix (#6239) | hace 5 años |
| CHANGELOG.md | 2b4b9be8cd Update CHANGELOG for Firestore v1.18.0 (#6470) | hace 5 años |
| CMakeLists.txt | 2a8d069b77 Run integration tests from CMake on mac (#4276) | hace 6 años |
| README.md | 2656033eb2 Update integration testing docs (#5490) | hace 6 años |
| test.sh | 5930ad2fee Factor out a universal build script (#884) | hace 8 años |
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
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.)
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.
scripts/run_firestore_emulator.sh and leave it running.Firestore_IntegrationTests_iOS scheme (or macOS or tvOS).Occasionally it's useful to run integration tests against a production account.
GoogleServices-Info.plist
file in Firestore/Example/App.If you want to switch back to running integration tests against the emulator:
GoogleServices-Info.plist is in its default state (git
checkout Firestore/Example/App/GoogleServices-Info.plist).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.