openradar-mirror
commented
8 years ago Modified: 2016-01-15T18:28:04.063340
Open openradar-mirror opened 8 years ago
openradar-mirror
commented
8 years ago Modified: 2016-01-15T18:28:04.063340
Description
Summary: After upgrading to Xcode 7.3 beta 1, the UI Testing output from XCTRunner is no longer being printed to stdout. There is no information from the UI Tests indicating which test cases/suites passed or failed, nor is there the usual XCTRunner log of the UI steps being taken during the tests.
If this was an intentional change, there needs to be a way to export test results so that UI Testing is able to be integrated with CI systems.
Related: rdar://24184959
Steps to Reproduce: Terminal: xcodebuild -workspace 'MyApp.xcworkspace' -scheme 'MyApp Debug' -destination 'id=${id}' clean test
Expected Results: The full xcodebuild stdout: Clean, then stderr output (below), Build, Codesign, and the Test output (XCTRunner log of the Test Suites, Test Cases, and the individual steps taken in each Test Case).
stderr: xcodebuild[...] [MT] IDETestOperationsObserverDebug: (...) Beginning test session ... with Xcode 7D111g on target <DVTiOSDevice: ...> {}
Actual Results: No XCTRunner output in Terminal. stdout output ends with codesigning of MyAppUITests-Runner.app. stderr does display TEST FAILED, that is the last statement.
Prior to that stderr also prints some MDMCreateDeltaDirectory and __MDMDirectoryDiff_block_invoke37 commands while the tests are running, and xcodebuild prints some iPhoneConnect statements.
Version: Version 7.3 beta (7D111g)
Notes: ~/Library/Developer/Xcode/DerivedData/MyApp-{...}/Logs/Test does contain new TestSummaries.plist files, and the Attachments also contains new screenshots and other test files. So logging is getting written somewhere, just not in a form that's easily exportable.
Product Version: Version 7.3 beta (7D111g) Created: 2016-01-15T00:12:39.185290 Originated: 2016-01-14T00:00:00 Open Radar Link: http://www.openradar.me/24195682