Skip to content

Latest commit

 

History

History
190 lines (125 loc) · 8.96 KB

CHANGELOG.md

File metadata and controls

190 lines (125 loc) · 8.96 KB

Installation/Updating

To install Subliminal see the installation walkthrough on the wiki.

To update Subliminal:

  • If you installed Subliminal manually, download Subliminal from the Releases page and drop in the new sources.
  • If you installed Subliminal using Git submodules, execute git checkout <tag> from Subliminal's root directory and commit your change in your project.
  • If you installed Subliminal using Cocoapods, update your Podfile (optional) and then execute pod update Subliminal from your project directory.

Then, to update your installation of Subliminal's docs (if desired), execute rake install from Subliminal's root directory (if you installed Subliminal manually or using Git submodules) or from YOUR_PROJECT_DIR/Pods/Subliminal (if you installed Subliminal using Cocoapods).

Please also see the notes below for release-specific update instructions.

Master

Complete diff

Updated Requirements
  • The upcoming 1.2 release will continue to support iOS 5.1, though it is likely to be the last release to do so.
Features

  • Tests and test cases can be tagged, and the SL_TAGS environment variables used to specify tests and test cases to run in CI. Jeffrey Wear #233

  • Tests and test cases can be conditionally run based on environment variables. Jeffrey Wear #233

  • Application (non-system) alerts can be manipulated directly. Justin Martin #228

  • subliminal-test can be directed to test a pre-built application. Justin Martin #218

  • SLAssert macros can be used outside of SLTest methods. Justin Martin #217

  • Class objects can be used as arguments to app hooks. Justin Martin #204

New SLElement subclasses
Bug fixes

  • +[SLTest supportsCurrentPlatform] returns NO if no tests cases support the current platform. Jeffrey Wear #233

  • subliminal-instrument properly logs Unicode text. Justin Martin #231

  • Alert handlers wait for alert elements to become valid. Justin Martin #230

  • Subliminal catches exceptions thrown by alert handlers. Justin Martin #230

  • Text field/view -setText: methods wait for elements to be valid before typing in them. Justin Martin #229

  • Elements can be matched within alert views. Justin Martin #228

  • Environment variables are properly exported when running CI tests on devices. Kevin #226

  • Elements are reported as visible if they are on-screen, regardless of which window they are in. Jeffrey Wear #215

  • Elements can be matched within table view header and footer views. Justin Martin #213

  • Elements can be matched within windows other than the key window. Justin Martin #202

  • Text views can be matched within table view cells. Justin Martin #202

1.1

Complete diff

Because of the significant period of time between the 1.0.1 and 1.1 releases, the 1.1 changelog is heavily abridged.

Updated Requirements
  • Subliminal now requires Xcode 5.1. To test in the iOS 5.1 Simulator, users must run OS X 10.8 and manually add the iOS 5.1 Simulator to Xcode as described here.
  • Subliminal no longer requires the user's password to run from the command-line. Users should stop passing the -login_password and --live options to the subliminal-test script and instead pre-authorize their computers to run Instruments.
Notable features
New SLElement subclasses
Other API additions
Notable bug fixes

  • Workaround isVisible not working in non-portrait orientations
    Jeffrey Wear #180

  • Fix interacting with collection view cell contents by including mock views in the accessibility path
    Jeffrey Wear #179

  • Detect the simulator launching in an inconsistent state (Travis CI Stability improvement)
    Jeffrey Wear #148

  • Guard against nil in accessibilityElementAtIndex:
    Chad Etzel #125

  • Search for the deepest element within the element hierarchy (iOS 7 fix)
    Nanouk #116