StanwoodUITesting framework

Table of contents

• Author
• Installation
• Usage
• Licence

Author

Tal Zion [email protected]

Installation

target 'Project_Tests' do
      inherit! :search_paths
      pod 'StanwoodUITesting'
end

Usage

iOS Develop Usage

Step One - Set up the testing tool

1. Add a new XCTestCase to the UI Test target and import StanwoodUITesting

   import XCTest
   import StanwoodUITesting
   
   class StanwoodTests: XCTestCase {
   
       let app = XCUIApplication()
   
       override func setUp() {
           super.setUp()
   
       }
   
       override func tearDown() {
           // Put teardown code here. This method is called after the invocation of each test method in the class.
           super.tearDown()
       }
   }

2. Let's configure and launch the sdk

   Add this to the setUp() function

   let app = XCUIApplication()
   var testingManager: UITesting.Manager!
   
   override func setUp() {
       	super.setUp()
   
       	continueAfterFailure = false
   
       	let slack = UITesting.Slack(webhookURL: URL(string: "webhook")!, channelName: "#channel")
       	guard let configurations = UITesting.Configurations(bundleId: "com.company.example", version: "1.0", app: app, slack: slack) else { return }
       
       	testingManager = UITesting.Manager(configurations: configurations, target: self)
       	testingManager.launch()
    }

3. Now we are ready to set up the test case

   func testStanwood(){
   	testingManager.runTests()
   }

   testingManager.runTests() will run the tests and report if there are any failures.

Step Two - Configure your project

Overview

The test navigation works by querying XCUIElement & XCUIElementQuery types. Check out the navigation types for a full list here. The UI Testing tool identifies each element by either an index, or a key, for example:

// Index
buttons.element(boundBy: index)

// Key
buttons[key]

What we need to do?

We need to set an accessibilityIdentifier for each element. This can be done in Xcode, in the utilities panel under the identity inspector.

You are starting to feel this may take too long! Say no more... This is handled for you, all you have to do is follow 3 simple steps:

1) Add `pod 'StanwoodCore` to your podfile
2) import StanwoodCore in any .swift files that contains UI elements
3) When setting labels/text, you have two options:
	a) Set the localised KEY in interface builder, i'e "MY_KEY_TITLE"
	b) Set `.localisedText` instead of `.text`.
	Note> It is required that you do not localise the key, rather then pass in the key. This will get handled by StanwoodCore

StanwoodCore Full Doc

PM Usage

Overview

The UI Testing tool works by querying element types from the views hierarchy and they can be accessed by calling a custom key or an index. For example, if we look at the image below from develop.apple.com, we can see how the elements are laid out.

This is a great example where we have a top UIView, which can be identified with a key, and a UICellectionView, which cells can be identified with an index.

Let's create our first test case

1. First, we want to set the schema JSON format

   {
   	"test_cases" : [
   
   	]
   }

2. Creating a test case

   {
   	"test_cases": [
   		"id" : "1",
   		"title": "Images Test",
   		"description": "Testing if the fifth image is tappable"
   	]
   }

3. Setting navigation action to support the test case

   The navigation is a collection of navigation actions. We need to set navigation items to navigation to what we want to test. For example, let's set navigation items according to the example above.

   Let's assume this view is on:

   • The second tab can be access with tabs as index 1

   • And the images view is accessed by tapping a button in the tab's rootView with an identifier of pierIdentifier

   • The fifth image can be access with cells at index 4

      {
      	"test_cases": [
      		"id" : "1",
      		"title": "Images Test",
      		"description": "Testing if the fifth image is tappable",
      		"navigation" : [
      			"tabs[1].action.tap",
      			"buttons['pierIdentifier'].action.tap",
      			"cells[4].action.tap"
      		]
      	]
      }

4. Now, let's say we want to test the image at position 11, which cannot be accessed in the view, we can set different actions, like swipeUp, swipeDown. For example:

   {
   	"test_cases": [
   		"id": "1",
   		"title": "Images Test",
   		"description": "Testing if the fifth image is tappable",
   		"navigation": [
   			"tabs[1].action.tap",
   			"buttons['pierIdentifier'].action.tap",
   			"cells[4].action.swipeUp",
   			"cells[10].action.tap"
   		]
   	]
   }

For the full action list, please check here

For the full navigation types, please check here. The UI Testing tool identifies each element by either an index, or a key.

Note: Element identifiers will be listed in each project documentation under UI Testing Identifiers

System Alerts

StanwoodUITesting supports system alerts. To monitor system alerts, simply add .monitor to any navigation handle.

	{
		"test_cases": [
			"id": "1",
			"title": "Images Test",
			"description": "Testing if the fifth image is tappable",
			"navigation": [
				"tabs[1].action.tap",
				"buttons['pierIdentifier'].action.tap.monitor",
				"cells[4].action.swipeUp",
				"cells[10].action.tap.monitor"
			]
		]
	}

Screenshots

Screenshots have been integrated and has been added to the action list. To take a screenshot, add action.screenshot.

To enable screenshots, add Environment Variable into the scheme Name: SRCROOT, Value: ${SRCROOT}

	{
		"test_cases": [
			"id": "1",
			"title": "Images Test",
			"description": "Testing if the fifth image is tappable",
			"navigation": [
				"action.screenshot",
				"tabs[1].action.tap",
				"buttons['pierIdentifier'].action.tap.monitor",
				"cells[4].action.swipeUp",
				"action.screenshot",
				"cells[10].action.tap.monitor"
			]
		]
	}

Release Notes

0.1.5

• Adding navigationBars support
• Improving error handling
• Removing some unused keys

Licence

StanwoodUITesting is under MIT Licence. See the LICENSE file for more info.