Releases: MobileNativeFoundation/bluepill
2.3.0: Support for Xcode 9.3
With this release Bluepill adds support for Xcode 9.3.
If you need Xcode 9.2 support, please check out the xcode-9.2 branch or use an older release.
Other changes in it:
New Features
- Added the ability to provide a simulator preferences file for setting AppleLocale and languange for simulator
- Build and test on CircleCI 2.0
Bug Fixes
- Remove trailing "()" from test name extracted from xctestrun file
- Fixed bluepill versioning for homebrew
- Fixed test hang when there is test timeout
2.2.0: Support for Xcode 9.2
This release is mainly for supporting Xcode 9.2.
Other changes in it:
New Features
- Add a warning when the number of processes used reaches 75% of the system's
maxproc
parameter. Not needed in High Sierra since process management there is dynamic. - Added the ability to provide a simulator preferences file. This can be used to set the system language of the simulator for example.
Bug Fixes
- Fix a memory allocation bug that reduces memory consumption dramatically.
- Fix a bug where test cases had to be passed with parenthesis in their names. (e.g.
foo/bar()
in order for Bluepill to recognize them. Now you can just passfoo/bar
). - Fix a problem where a hanging test would hang the
bp
process. - Reduce CPU consumption by checking for the App process every second instead of immediately after we've just checked.
POTENTIAL INCOMPATIBILITY
JUnit reporting now properly uses the errors and failures classifications. Before everything was being lumped under failures.
2.1.0: Support for Xcode 9.1
With this release Bluepill adds support for Xcode 9.1.
If you need Xcode 9.0 support, please check out the Xcode-9.0
branch or use an older release.
2.0.2
2.0.1 Disabled DEBUG log to reduce console output
This release disabled DEBUG log from printing out to console. Previous release 2.0.0 print out a lot of DEBUG log to console.
2.0.0
This release brings Xcode 9 support to Bluepill.
- Xcode 8 support has been moved to the
xcode8
branch. Note that this branch does not work with Xcode 9.0. - Running bluepill using schemes has been deprecated (the
--scheme-path
option). You should switch to using xctestrun files (--xctestrun-path
option). This fixes a bunch of bugs with environment variable expansion. The.xctestrun
files are produced when you use thebuild-for-testing
subcommand inxcode-build
.
1.1.2
1.1.1 support for reading xctestrun file
Bluepill v1.1.1
Support for reading .xctestrun
file. Now instead of passing in the app, scheme and test bundle path, we are able to parse the .xctestrun
file and instruct bluepill
to its job.
Note:
You must run build-for-testing if you use xcodebuild in terminal.
./bluepill --xctestrun-path ./SampleAppTest_iphonesimulator10.3-x86_64.xctestrun -o ./output/
1.1.0 Reuse Simulators
With this release, Bluepill supports reusing simulators between test bundles to save the long boot time. To enable it, add the --reuse-simulator
option to the bluepill command line or add "reuse-simulator" : true
to the json configuration file.
The balancing issue of tests to run after excluding skipped tests is also fixed.