Releases: bitrise-steplib/steps-xcode-test
2.3.2
2.3.1
2.3.0
New input:
disable_index_while_building
: If it is set to yes
it will add the COMPILER_INDEX_STORE_ENABLE=NO
flag to the xcodebuild
command which will disable the indexing during the build.
This could make the build faster by skipping the indexing during the build run.
Indexing is needed for
- Autocomplete
- Ability to quickly jump to definition
- Get class and method help by alt clicking.
- Which are not needed in CI environment.
Disable it locally:
In Xcode you can turn off the Index-WhileBuilding feature
by disabling the `Enable Index-WhileBuilding Functionality` in the `Build Settings`.
Disable it via xcodebuild:
In CI environment you can disable it by adding `COMPILER_INDEX_STORE_ENABLE=NO` flag
to the `xcodebuild` command.
Fix:
Export BITRISE_XCRESULT_PATH
even if the test fails. #112 - Thanks @ollitapa
2.2.0
Export .xcresult's path at the end of the step
Since 2.1.0 the step uses the -resultBundlePath flag for the xcodebuild command which will replace the result files to the provided path.
This fix will export the BITRISE_XCRESULT_PATH
env which points to the generated .xcresult
package.
2.1.2
2.1.1
2.1.0
Fixed an issue, where exporting screenshots did not succeed in case of failing UI tests, with the error message:
Failed to update screenshot names, error: screenshot not exists
.
Exported screenshots have a different format, which now contains the test identifier, ios_simple_objcUITests-testExample_2019-01-10_11-05-49_screenshot_A0E6A26C-40C4-49E0-BBCB-47C9D023E772.png
instead of the previously used 2019-01-10_11-02-59_Screenshot of main screen (ID 1)_1_F970609B-056A-4F4F-A337-FB586A03EDE5.png
. Failing tests' screenshots are now placed under the Failures
directory.
Fixed an issue occurring in a development environment, in the case if the XCode DerivedData directory contained different builds of the same project:
Failed to export UI test artifacts, error more than 1 project derived data dir found
.
2.0.0
We removed the wait_for_simulator_boot
input from the step and introduced the headless_mode
input instead.
With headless mode enabled the step will not force the simulator to boot in the foreground. Instead, xcodebuild will run the tests in the background.
Migration Guide
Moving from v1 to v2:
The v1.x version of the step will always force start the simulator and with default configuration the step will wait for a fixed 40 seconds for the simulator boot.
The v2.x version of the step will run in headless mode by default and will not start the simulator. Instead, xcodebuild will run the tests in the background.
In headless mode the simulator will not be visible but the tests will run in the same way (even the screenshots will be captured).
If you want to see the test run you can force start the simulator by disabling the headles_mode
input. In this case the step will boot the simulator and it will wait for the simulator to boot.
1.18.17
1.18.16
- Install xcpretty output tool if missing
- go-test update in bitrise.yml