| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| sample-xcode.xcresult/ | 08-Apr-2025 | - | 31 | 30 | ||
| README.md | D | 08-Apr-2025 | 694 | 19 | 13 | |
| test_output.json | D | 08-Apr-2025 | 14.1 KiB | 625 | 624 | |
| tests_reference_output.json | D | 08-Apr-2025 | 11.1 KiB | 278 | 277 | |
| xcresult_output.json | D | 08-Apr-2025 | 12.7 KiB | 503 | 502 |
README.md
1# Test Data 2 3## [sample-xcode.xcresult](./sample-xcode.xcresult) 4 5This is an example benchmark `xcresult` directory that is the result of running an `xcodebuild`. 6 7An example invocation might look something like: 8 9```bash 10xcodebuild test -project $SRCROOT/benchmark-darwin-samples-xcode.xcodeproj \ 11 -scheme testapp-ios \ 12 -destination id=7F61C467-4E4A-437C-B6EF-026FEEF3904C \ 13 -resultBundlePath $SRCROOT/benchmark-darwin-samples-xcode.xcresult 14``` 15 16The `xcresult` output directory stores results in a nested `plist` format. Entities in the top-level 17`plist` file point to other entities stored in other`plist` files (inside the `Data` directory), 18using a unique filename identifier. 19