Creating a UI Test project

1. Add the NuGet package of Zebble.Testing to your solution.
2. Add a new shared project to your solution named "UITests".
3. Add a reference to the shared project from your platform specific projects (UWP, Android, iOS)
4. In Startup.cs file, change the LoadFirstPage() method to the following:

5. // Change to true and run when you want to activate the test mode
   const bool TestExecutionMode = false; 
    
   public static async Task LoadFirstPage()
    {
         await Nav.Go(new Pages.MyStartPage()); 
         if (TestExecutionMode)      
              Zebble.Testing.TestEngine.Run();
    }

Creating a test 

In your UITests project add a test class. Name it after the scenario that you want to test, for example "ManageContacts". It should inherit from TestScenario in Zebble.UITesting namespace and implement the Run() method.

namespace UITests
{
    using System;
    using Zebble.UITesting;
    using System.Threading.Tasks;

    class ManageContacts : UITest
    {
        public override Task Run()
        {
            Tap("Contacts");
            ExpectHeader("Contacts");

            // Test adding a contact:
            Tap("Add");
            Set("First name").To("Jack");
            Set("Last name").To("Williams");
            Tap("Save");
            Expect("Jack Williams");

            // Test deleting a contact
            AtRow("Jack Williams").Swipe(SwipeDirection.Left);
            AtRow("Jack Williams").Tap("Delete");
            ExpectNo("Jack Williams");
        }
    }
}

UI Testing Commands

You can invoke any of the following commands as part of your test script:

• Tap("my button")
• Set("some field").To("some value")
• ...

Locators and Context 

Often you can have several objects on the screen with the same text. To resolve ambiguity, you can use one or a combination of location specifiers from the following list:

• Near("something")
• Above("something")
• ...