I love what I'm seeing about MX*Diagnostic (MXCrashDiagnostic and friends) and the capability to use it to track down crashes and issues. What I'd like to know is if there's a way I can trigger the diagnostic output deterministically at the end of the CI-driven integration test so that I can build in a scan for these and harvest them to help identify regressions.
Without such na mechanism, am I left having to leave the device (or simulator) running for a huge amount of time and hope for the best? I want to use this specifically with CI, which may have multiple runs per day - and would like to identify which runs of code were aligned without something akin to a "spend a day testing this single iteration of the code" kind of constraint.
Without such na mechanism, am I left having to leave the device (or simulator) running for a huge amount of time and hope for the best? I want to use this specifically with CI, which may have multiple runs per day - and would like to identify which runs of code were aligned without something akin to a "spend a day testing this single iteration of the code" kind of constraint.
