Releases: bitrise-steplib/steps-xcode-test
Releases · bitrise-steplib/steps-xcode-test
4.0.1
4.0.0
Revamped the step's input structure.
- Replaced
simulator_device
,simulator_os_version
, andsimulator_platform
inputs withdestination
. This is passed toxcodebuild
as the-destination
parameter. For example, if you previously usedsimulator_device: iPhone 8 Plus
,simulator_os_version: 15.0
, andsimulator_platform: iOS Simulator
,destination
should beplatform=iOS Simulator,name=iPhone 8 Plus,OS=15.0
. - New input: Build settings (
xcconfig_content
). Allows you to override the project's build settings. Creates a temporary file with the given input value as content and passes it toxcodebuild
as the-xcconfig
parameter. - Renamed
is_clean_build
input toperform_clean_action
. - Renamed
xcodebuild_test_options
input toxcodebuild_options
. - Renamed
output_tool
input tolog_formatter
. - Renamed
xcpretty_test_options
input toxcpretty_options
. - Renamed
verbose
input toverbose_log
. - Removed
export_uitest_artifacts
input since this is no longer supported on modern Xcode versions. - Removed
generate_code_coverage_files
input in favor ofxcconfig_content
. If you'd like to generate legacy code coverage files, you should addGCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES
andGCC_GENERATE_TEST_COVERAGE_FILES=YES
separated by newline characters (\n
) to thexcconfig_content
input. - Removed
disable_index_while_building
input since this is no longer an issue on modern Xcode versions. - Removed
single_build
input becauseshould_build_before_test
is removed (they were used in conjunction). - Removed
should_build_before_test
input since this is no longer an issue on modern Xcode versions. - Re-organized categories.
- Updated titles, summaries, and descriptions.
3.1.0
3.0.2
3.0.1
3.0.0
Added Xcode Test Repetition support (available in Xcode 13+).
- New step inputs:
Test Repetition Mode
,Maximum Test Repetitions
, andRelaunch Tests for Each Repetition
. Test Repetition Mode
allows you to run your tests repeatedly in various ways, such as retry on failure and run until max repetitions. There are 4 options you can choose from:none
: The tests won’t repeat.until_failure
: Repeats a test until the test fails or until the maximum repetition.retry_on_failure
: Failed tests run until they succeed or until the repetition number you specify.up_until_maximum_repetitions
: Reruns all tests until maximum test repetition is reached regardless of the test outcomes.
Maximum Test Repetition
lets you specify the maximum number of times a test will repeat based on Test Repetition Mode.Relaunch Tests for Each Repetition
will launch tests in a new process for each repetition if enabled.
Should retry tests on failure?
step input is no longer available in Xcode 13+.
- If you enable
Should retry tests on failure?
in Xcode 13+, your builds will fail with an error. - We recommend using the
retry_on_failure
Test Repetition Mode instead (see above). This will retry only your failed tests and won't restart the whole test suite.
2.7.1
2.7.0
Added support for Xcode Test Plan and improved failed test retry.
- New step input:
test_plan
. - Starting from Xcode 13, failed tests will be retried using Xcode Test Repetition (if
should_retry_test_on_fail
is enabled). - Replaced
BITRISE_XCODE_RAW_TEST_RESULT_TEXT_PATH
environment variable withBITRISE_XCODEBUILD_BUILD_LOG_PATH
andBITRISE_XCODEBUILD_TEST_LOG_PATH
. .xcresult
is now deployed as a ZIP artifact and exposed under theBITRISE_XCRESULT_ZIP_PATH
environment variable.