Skip to content

Latest commit

 

History

History
83 lines (52 loc) · 5 KB

CHANGELOG.md

File metadata and controls

83 lines (52 loc) · 5 KB
Raw

CHANGELOG

Pending

1.6.0

  • Added Image element which can be used to represent images (and anything else that XCUI sees as a .image type). (issue #100)
  • Added Brewfile for better dependency control
  • Fixes an issue when building Carthage framework failed due to a missing file in TABTestKit carthage project.
  • Adds a step script for building carthage framework in Travis CI. This should report to CI if the TABTestKit can be build as a Carthage framework.
  • Adds a step script for linting cocoapods project in Travis CI. This should report to CI if the TABTestKit can be safe to be published as Cocoapods framework.

1.5.0

  • Added support for deep linking by adding a new function to NavigationContext which allows you to pass any URL to open, including regular HTTPS or app-specific URLs. (issue #94)
  • Added globally available instance of Springboard meaning you no longer need to create one every time you want to use Springboard as a parent element. (issue #93)
  • Added Icon element which can be used to represent home screen icons (and anything else that XCUI sees as an .icon type). (issue #95)
  • Added support for waiting for the app to be in a particular state in AppContext (useful for deep linking)

1.4.0

  • Improved error messaging with XCTAssert* calls. The main offender was when waiting for an element to be in a specific state and it would just show an error of XCTAssertTrue failed. (issue #80)

1.3.0

  • Better failure reports. Specifically, the most recently executed Step's file / line is used to report a failure (if one exists). This means that the red error banner now shows on the correct line in the correct file, and should report better failures on CI rather than just "assert true failed in Element.swift" etc. (issue #80)

1.2.1

Fixed

  • Properly clears launch argument indicating that the app should be launched clean when calling launchTheApp(clean:) in AppContext. (issue #74)
  • Fixes an issue when calling background() on BaseApp on iOS 13 since it never reaches the runningBackgroundSuspended state. This is likely a bug in iOS 13 simulators/XCUI but this is fixed by just waiting for runningBackground for iOS 13+. (issue #64)

1.2.0

New features

  • Clears launch arguments and launch environment values as part of tearDown, ready for the next test.
  • Added new ActivitySheet to represent the UIActivityViewController sheet.
  • Added support for Carthage, which allows project to use TABTestKit using Carthage as their dependency manager.

Fixed

  • Renames func keyboard(isType type: Keyboard.KeyboardType) to func keyboardType(is type: Keyboard.KeyboardType) to avoid conflict with public let keyboard = Keyboard() within KeyboardContext.

1.1.0

New features

  • Added option to provide multiple states when using InteractionContext to scroll until an element in a particular state or multiple states.
  • Added option to scroll until some element is not in a state (or multiple states).
  • Added a new visibleIn State case, which takes a different element that the element must be visible in, unlike the existing visible case which just uses whatever the parent element is.
  • Added a new from(to) Direction case, which allows you to provide a from and to coordinate to scroll from and to. This is useful, for example, when trying to avoid the keyboard while scrolling.
  • Added CGVector helper constants for representing various positions in the element's space, like .middle, .topLeft, .bottomThird. These can be used on their own, or with the new Direction case mentioned above.
  • Updated the docs for CellContaining to be clearer about how it works with cell reuse.
  • Added a new ScrollableScreen protocol, which is a special protocol you can make your screen structs conform to instead of Screen. To conform to ScrollableScreen, your trait must be any element that is also Scrollable (like ScrollView or Table). By doing that, you automatically get scrolling behaviour on the screen so you can pass the screen instance in directly to InteractionContext when scrolling.
  • Added new Keyboard element, which can be used anywhere that Element can, and more usefully be used to assert to right keyboard type is shown on-screen. You can also use Keyboard to find the topCoordinate of it to avoid it while scrolling or performing gestures.
  • Since there can only be one software keyboard shown on-screen at one time, an instance is globally available in your tests.
  • Added new KeyboardContext which TABTestCase already conforms to.
  • Added frameInScreen property to all Elements, which allows you to use the CGRect of the element in relation to the device's screen.
  • Improved the default Scrollable implementation to avoid the keyboard while scrolling.

Fixed

  • Added a workaround for iOS 13, where UILabels with the .header accessibility trait are always seen as .staticText by XCUI regardless.

1.0.0

Initial release of TABTestKit, check out the README!