Skip to content

Releases: bitrise-steplib/steps-xcode-test

1.13.1

17 Mar 14:09
Compare
Choose a tag to compare
  • deprecated simulator_device=iPad will be replaced with simulator_device=iPad 2

1.13.0

16 Mar 13:09
Compare
Choose a tag to compare
  • NEW input: xcodebuild_test_options for additional options for xcodebuild build test call
  • boot simulator before run test

1.12.1

02 Mar 16:40
Compare
Choose a tag to compare
  • xcodebuild build command use the same derived data dir as xcodebuild test command

1.12.0

12 Feb 16:05
Compare
Choose a tag to compare
  • New input: export_uitest_artifacts - to export UITest screenshots and other artifacts into the BITRISE_DEPLOY_DIR as a compressed ZIP file
  • If build fails, raw xcodebuild output log will exported into BITRISE_DEPLOY_DIR as a compressed ZIP file

1.11.0

25 Jan 14:15
Compare
Choose a tag to compare
  • is_clean_build is now set to "no" by default

1.10.0

09 Jan 11:39
Compare
Choose a tag to compare

New output BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH : contains the path of the raw xcodebuild output. Even if you use a different output tool this file will contain xcodebuild's output.

Related request & discussion: #29

1.9.0

30 Dec 08:27
Compare
Choose a tag to compare
  • NEW OPTION : simulator platform - can now be set to tvOS, to run tvOS app unit tests

1.8.0

05 Dec 17:07
Compare
Choose a tag to compare
  • Removed the custom "build summary" scan which was built into the step
  • Instead you can now select xcpretty as the output tool
  • xcpretty's HTML report also replaced our previous raw .log report
  • You can, of course switch back to the raw xcodebuild output, by setting the output_tool option to xcodebuild, the default value is xcpretty

1.7.0

09 Nov 12:00
Compare
Choose a tag to compare
  • output BITRISE_XCODE_TEST_FULL_RESULTS_TEXT replaced with saving the Summary into a file instead, as the Test Summary might be larger than what common tools can process as an Environment Variable

1.6.0

28 Oct 15:30
Compare
Choose a tag to compare
  • option to enable/disable Xcode code coverage reporting