Add iOS crash report creation steps in Tests README

MacSymbolicatorTests/README.md

@@ -11,12 +11,20 @@ For validating the behavior of MacSymbolicator, we need to follow these steps:
  - Run `create_crashes_samples_spindumps.sh` from the extracted directory (requires sudo to sample/spindump processes)
  - This script will create a `Result.zip` that we will transfer back to the first computer
 3. Back on the main computer, extract `Result.zip` into `MacSymbolicatorTests/Resources`
-4. Create the "expect output" of symbolication
+4. Create the iOS crash report
+ - Install `Binaries/iOSCrashingTest.app` on your iOS device (Xcode's Devices & Simulators, select device, drag & drop .ipa)
+ - Launch app on iOS device, it will crash
+ - Transfer the .ips crash report from the iOS device to your computer
+  - Can be found in Settings > Privacy & Security > Analytics & Improvements > Analytics Data > iOSCrashingTest-...
+  - Can be sent using AirDrop
+ - Move & rename it to `Resources/Crashes/ios-crash.ips`
+
+5. Create the "expect output" of symbolication
  - Run `MacSymbolicatorTests/create_expected_output.sh`
  - This script will build `MacSymbolicatorCLI` and use it to symbolicate the reports from the second computer
  - This script will save the symbolicated output files suffixed with `_symbolicated`
-5. Manually check that the expected output is symbolicated correctly
-6. Run the tests in Xcode, which will symbolicate the reports and compare them to the expected output
+6. Manually check that the expected output is symbolicated correctly
+7. Run the tests in Xcode, which will symbolicate the reports and compare them to the expected output
 
 
 ### Q&A
@@ -25,5 +33,5 @@ For validating the behavior of MacSymbolicator, we need to follow these steps:
  - So that we don't have include all the binaries, the dSYMs, the samples, and spindumps which are pretty big for git, pollute the history, but also might contain information about my computer that I don't want to share.
 - For step 2, why need a second computer?
  - If you use the same computer that created the crashing binary (and dSYM), when macOS creates a crash report for an app it will also automatically symbolicate it. My guess is that dSYMs are indexed by Xcode as soon as they're created.
-- For step 5, doesn't manually checking the output defeat the point of automated testing?
+- For step 6, doesn't manually checking the output defeat the point of automated testing?
  - Yes, but at least the expected output is created automatically which saves a LOT of time.