Open the solution in Xamarin Studio. Notice that the Xamarin project already has the Xamarin Test Cloud Agent installed via NuGet.

Size: px

Start display at page:

Download "Open the solution in Xamarin Studio. Notice that the Xamarin project already has the Xamarin Test Cloud Agent installed via NuGet."

Samantha Golden
5 years ago
Views:

1 Calabash Quickstart for Xamarin.iOS Overview In this quick start we'll add a Calabash feature to a Xamarin.iOS application and run the test locally and in Xamarin Test Cloud. The test will confirm that the application will display the correct error message when the user enters a credit card number that is too short. Conceptually, the test will be compromised of the following steps: 1. Wait for the View Controller to load Typically a view controller is quick to load, but to be safe the test will verify that the correct view controller has loaded. 2. Enter 15 digits for the credit card number The test must simulate data entry. 3. Tap the Validate Credit Card button Simulate what a user would do to call the validation logic. 4. Confirm the Error Message Finally, the test should assert the application has displayed the correct error message. To save time, download the ZIP file that contains the sample application. Open the solution in Xamarin Studio. Notice that the Xamarin project already has the Xamarin Test Cloud Agent installed via NuGet. Run the application to confirm that the application builds and runs in your development environment. This will also compile the application and install on the simulator. You will not be able to run your Calabash tests using Visual Studio. Requirements This quickstart assumes you are using Xamarin Studio 5.9 or higher. It is assumed that you already have installed the Calabash Ruby gems. It is not possible to run Calabash tests against Xamarin.iOS using Windows. Create the features Folder

The features folder is a special folder where Cucumber expects the test code to reside. Calabash can create this folder and provide some boilerplate code to get us started.

2 The features folder is a special folder where Cucumber expects the test code to reside. Calabash can create this folder and provide some boilerplate code to get us started. Start up a Terminal session, and change the working directory to the project folder, i.e.: In the project folder, run calabash-ios as shown below: $ calabash-ios gen Question I'm about to create a subdirectory called features. features will contain all your calabash tests. Please hit return to confirm that's what you want Info Features subdirectory created. Make sure you've build your -cal scheme in XCode and try executing cucumber This has created a features folder with the following structure:

3 Lets move on to create the first test. Creating the First Test To create the first test, edit the file features/my_first.feature and replace the existing contents with the following: Feature: Credit card validation. Credit card numbers must be exactly 16 characters. Scenario: Credit card number is too long Given I wait to see a navigation bar titled "Simple Credit Card Validator" When I enter " " into input field number 1 When I touch the "Validate Credit Card" button Then I should see "Credit card number is too long." Here is a quick description of this snippet: A Feature must have name, and my optionally provide a description. A Feature is broken down into Scenarios. A Scenario is a formal example of how the Feature (or a rule in the Feature) works. Scenarios, in turn, are broken down into Steps. We will write code that implement the Steps and allow Calabash to test our application. Running the Test in the ios Simulator

4 The test is complete and it can be run at command line usingcucumber. Run cucumber in the same directory that contains the features folder. You should see the following output: $ cucumber Feature: Credit card validation. Credit card numbers must be exactly 16 characters. Scenario: Credit card number is too long # features/my_first.feature:4 Given I am on the main screen # features/step_definitions/my_first_steps.rb:1 And I try to validate a credit card number that is 17 characters long # features/step_definitions/my_first_steps.rb:5 Then I should see the error message "Credit card number is too long." # features/step_definitions/my_first_steps.rb:14 1 scenario (1 passed) 3 steps (3 passed) 0m11.068s With the test passing locally, it's time to run it in Xamarin Test Cloud. To do this, we must first create a team *test run* in Xamarin Test Cloud. Running the Test in Xamarin Test Cloud If you want to run the tests in Xamarin Test Cloud there are three tasks to complete before actually submitting the tests: 1. Build an IPA You can build an IPA at the command line using xbuild in the features directory as shown below: /Library/Frameworks/Mono.framework/Commands/xbuild /p:configuration=debug /p:platform=iphone /p:buildipa=true /target:build../creditcardvalidator.ios.sln 2. Create a Gemfile. A Gemfile is a text file that tells Test Cloud what version of the gems your project uses. Create a text file in the directory that holds your Calabash features folder, and name it Gemfile. A sample Gemfile is shown below:

5 source ' gem 'calabash-cucumber', '0.16.3' gem 'calabash-android', '0.5.14' gem 'xamarin-test-cloud', '1.1.2' The gems and their version number listed should match the version number of the gems you have installed. 3. Create a Test Run This involves logging in to Xamarin Test Cloud, and creating a Test Run. The Creating a Test Run guide contains details how to do this. Once you have compiled the IPA and created the Test Run, you can upload the tests and IPA: $ test-cloud submit./bin/iphone/debug/creditcardvalidator.ios-1.0.ipa $XTC_TEAM_API_KEY --devices <DEVICES_ID> --app-name "Simple Credit Card Validator" --user < _ADDRESS> Summary At this point you have finished this quick start. For practice, why not try to writing the remaining Scenarios for this feature.

ArcGIS Runtime SDK for.net Building Apps. Rex Hansen

ArcGIS Runtime SDK for.net Building Apps Rex Hansen Thank You to Our Sponsors Agenda Overview of the ArcGIS Runtime SDK for.net Resources for developers Common developer workflows: App templates, NuGet