# Xcode Test for iOS v2.4.6

**URL:** <https://discuss.bitrise.io/t/xcode-test-for-ios-v2-4-6/13182>\
**Category:** Changelog\
**Created:** [June 3, 2020, 1:45pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-4-6/13182 "2020-06-03T13:45:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [June 3, 2020, 1:45pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-4-6/13182/1 "2020-06-03T13:45:21Z")

</div>

When using `xcodebuild` _Output tool_, the Xcode raw build logs are no longer included in the Bitrise build logs, due to their large size. The Xcode build logs are available as an artifact uploaded by _Deploy to [Bitrise.io](http://Bitrise.io)_ step, and the output BITRISE\_XCODE\_RAW\_TEST\_RESULT\_TEXT\_PATH.

The `xcpretty` _Output tool_ is unchanged. The output is visible in the build log, and the raw logs are uploaded as an artifact only in case of a failure.

> **[bitrise-steplib/steps-xcode-test](https://github.com/bitrise-steplib/steps-xcode-test/releases/2.4.6)**
>
> Xcode Test step. Contribute to bitrise-steplib/steps-xcode-test development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [September 1, 2020, 1:45pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-4-6/13182/2 "2020-09-01T13:45:22Z")

</div>

This topic was automatically closed after 90 days. New replies are no longer allowed.