Bluepill alternatives and similar libraries
Based on the "UI Testing" category.
Alternatively, view Bluepill alternatives based on common mentions on social networks and blogs.
9.2 0.0 L1 Bluepill VS CucumberA home for issues that are common to multiple cucumber repositories
8.2 0.0 L5 Bluepill VS SwiftMonkeyA framework for doing randomised UI testing of iOS apps
6.2 0.0 L5 Bluepill VS ios-driverSelenium server to test native, hybrid and web apps on IOS. Join us on IRC #ios-driver on freenode
6.0 8.8 Bluepill VS Marathon RunnerCross-platform test runner written for Android and iOS projects
5.7 3.8 L5 Bluepill VS LayoutTest-iOSWrite unit tests which test the layout of a view in multiple configurations
4.4 0.0 Bluepill VS AutoMateSwift framework containing a set of helpful XCTest extensions for writing UI automation tests
Testing the UI without UI Testing, a Swift experiment.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Bluepill or a related project?
Bluepill is a tool to run iOS tests in parallel using multiple simulators.
- Running tests in parallel by using multiple simulators.
- Automatically packing tests into groups.
- Running tests in headless mode to reduce memory consumption.
- Generating a junit report after each test run.
- Reporting test running stats, including test running speed and environment robustness.
- Retrying when the Simulator hangs or crashes.
It is quick and easy to start using Bluepill!
- Get bluepill binary: build from source or use our releases. You can also get the binary from Homebrew.
$ brew install bluepill
- Build your app and test bundle. You must
build-for-testingif you use
- Run bluepill using the
.xctestrunfile generated by Xcode.
$ bluepill --xctestrun-path ./SampleAppTest_iphonesimulator10.3-x86_64.xctestrun -o ./output/
Alternatively, you can use a configuration file like the one below:
"xctestrun-path": "./SampleAppTest_iphonesimulator10.3-x86_64.xctestrun", # Relative path or abs path
"output-dir": "./build/" # Relative path or abs path
$ bluepill -c config.json
A full list supported options are listed here.
|Command Line Arguments
|The path to the host application to execute (your
|The path to the
.xctestrun file that xcode leaves when you
|The path of a json file which describes the test plan. It is equivalent to the
.xctestrun file generated by Xcode, but it can be generated by a different build system, e.g. Bazel
|Directory where to put output log files. (bluepill only)
|Read options from the specified configuration file instead of the command line.
|On which device to run the app.
|Exclude a testcase in the set of tests to run (takes priority over
|Run in headless mode (no GUI).
|Spawn simulator by clone from simulator template.
|Path to xcode.
|Include a testcase in the set of tests to run (unless specified in
|Only list tests and exit without executing tests.
|Number of simulators to run in parallel. (bluepill only)
|Print a configuration file suitable for passing back using the
|Number of times to recover from simulator/app crashing/hanging and continue running.
|Number of times to retry on test failures
|Only retry failed tests instead of all. Also retry test that timed-out/crashed.
|What runtime to use.
|Timeout in seconds for a test that seems stuck (no output).
|Timeout in seconds for a test that is producing output.
|The path to the test bundle to execute (single
|Additional XCTest bundles that is not Plugin folder
|Additional XCTUITest bundles that is not Plugin folder
|Number of times we'll run the entire test suite (used for load testing).
|Test bundles you don't want to be packed into different groups to run in parallel.
|Turn off all output except fatal errors.
|Enable collection of diagnostics in output directory in case of test failures.
|The test runner for UI tests.
|Directory where simulator screenshots for failed ui tests will be stored.
|Directory where videos of test runs will be saved. If not provided, videos are not recorded.
|Whether to keep the recorded video for passing tests. Deleted by default.
|A list of videos that will be saved in the simulators.
|A list of images that will be saved in the simulators.
|Skip Xcode version check
|Retry tests that crashed app and consider it non-fatal if it passes on retry.
The exit code of Bluepill uses bit indicators which could represent multiple exit status. Please refer to the header for meaning of each bit.
Bluepill officially supports Xcode 14.0. If you're looking for old Xcode support, please checkout the following branches:
- Xcode-10.0 | Xcode-10.1 | Xcode-10.2 | Xcode-10.3
- Xcode-11.0 | Xcode-11.1 | Xcode-11.2 | Xcode-11.3 | Xcode-11.4 | Xcode-11.5
- Xcode-12.0 | Xcode-12.2 | Xcode-12.3 | Xcode-12.4 | Xcode-12.5
- Xcode-13.0 | Xcode-13.1
If you're looking for newer Xcode version support, try using Bluepill with
unsafe-skip-xcode-version-check flag but make sure your app is tested with it and the underlying risks are understood.
If you're using Fastlane to run your tests, you're in luck! You can integrate Bluepill into your project with very little change to your existing setup. Just integrate one of the following Fastlane plugins, and you'll be on your way:
- Redpill - The most up-to-date plugin; it's is maintained by Omni and offers a full set of options to hook into Bluepill. As of this writing, Redpill is compiled against Xcode 9.1, and intended for use with CircleCI. It will be updated with newer versions of Xcode when CircleCI supports them.
- fastlane-plugin-bluepill - Last updated Nov. 7th, offers basic support for working with the Bluepill binary.
- Bluepillar - Last updated May 29th, it's the original fastlane plugin for working with Bluepill. It was inspired by this blog post.
- XBluepill - Last updated Jan 27th. It supports all Bluepill options. Thera are some differences from other plugins:
- Support Xcode 9.2
- No need to build your project before using the plugin. Builds you project by itself and put xctestrun file automatically;
- Can reset all simulators if needed (removes all current simulators and recreates default from scratch);
If you're using Bitrise.io as your CI/CD, you can start using Bluepill immediately. Just add the Bluepill Build/Test for iOS step to your existing workflow. This open source step is maintained by HealthEngineAU and supports Xcode 8.3 and later.
Q & A
- Are we able to run Xcode UI Testing bundle with Bluepill
YES, we recently added support for Xcode UI Testing bundles. Thanks to the inspiration from FBSimulatorControl. Bluepill now supports Xcode unit test bundle and UI test bundles.
- Easiest way to get Bluepill binary?
- How to test Bluepill in Xcode?
Select BPSampleApp scheme and build it first. Then you can switch back to
bluepill-cli scheme to run their tests.
- How to get Bluepill binary from source?
./scripts/bluepill.sh build to test and build Bluepill. The binary will be output in the ./build folder.
- How to test my changes to Bluepill?
- How to BUMP the max files and max procs to support running multiple simulators on macOS?