4.7 Testing iOS AUT's

You can write tests for iOS AUT's when you select the toolkit concrete, mobile or iOS in the Project properties.

Choose mobile if, at a future point, you will want to use this Project for cross-platform mobile testing.

When you select mobile as the Project toolkit, the library Projects unbound_modules_concrete and unbound_modules_mobile are automatically reused in your Project .

When you select iOS as the Project toolkit, the library Projects unbound_modules_concrete, unbound_modules_mobile and unbound_modules_iOS are automatically reused in your Project .

The actions in the concrete library are described in the reference manual -->Reference Manual .

• 4.7.1 Supported iOS AUT's
• 4.7.2 Setting up an iOS AUT for testing
  • 4.7.2.1 Add the library to your project files
  • 4.7.2.2 Create a Testing Target
  • 4.7.2.3 Configure the Testing Target
  • 4.7.2.4 Add hook into the AUT
  
  
• 4.7.3 Design for testability in iOS AUT's
  • 4.7.3.1 Naming components
  • 4.7.3.2 Adding support for text retrieval
  
  
• 4.7.4 Addressing the correct component in your iOS tests
• 4.7.5 Working with iOS components and actions
  • 4.7.5.1 Working with iOS switches
  • 4.7.5.2 Working with iOS Table Views (lists)
  • 4.7.5.3 Working with iOS tabbed controls
  • 4.7.5.4 Working with iOS pickers
  • 4.7.5.5 Working with gestures
  • 4.7.5.6 Working with the keyboard
  • 4.7.5.7 Working with unmappable (unsupported) components
  • 4.7.5.8 Other important information for testing iOS AUT's
  
  
• 4.7.6 Testing AUT's written with Monotouch
  • 4.7.6.1 Create a binding project
  • 4.7.6.2 Add the library to the binding project
  • 4.7.6.3 Setting up linker options
  • 4.7.6.4 Defining the API contract
  • 4.7.6.5 Building a .NET library
  • 4.7.6.6 Add hook into AUT