Features
Start a free trial

NUnit Automated App Testing

NUnit is a unit-testing framework for all .NET languages. You can use NUnit to run tests on mobile devices, together with Appium.

This documentation page will show you how to set up and run Appium tests with NUnit on TestingBot's remote physical device grid. Once you've finished integrating, you will be able to run tests on iOS and Android devices, in parallel, on the remote TestingBot device grid.

Installation

We'll assume you are using Visual Studio to run your tests.
Make sure to add these NuGet packages:

  • Appium.WebDriver
  • NUnit

Initialize remote Appium Webdriver

To be able to connect to TestingBot's device grid, we'll need to set up a remote Appium WebDriver. Please see the example file (TestingBotDriver) below on how to do this.

Copy code
using System;
using OpenQA.Selenium;
using OpenQA.Selenium.Appium;
using OpenQA.Selenium.Appium.Android;
using OpenQA.Selenium.Appium.Enums;

namespace testingbot
{
    [Binding]
    public sealed class TestingBot
    {
        private TestingBotDriver tbDriver;

        [BeforeScenario]
        public void BeforeScenario()
        {
            tbDriver = new TestingBotDriver(ScenarioContext.Current);
            ScenarioContext.Current["tbDriver"] = tbDriver;
        }

        [AfterScenario]
        public void AfterScenario()
        {
            tbDriver.Cleanup();
        }
    }

    public class TestingBotDriver
    {
        private AppiumDriver<AndroidElement> driver;
        private ScenarioContext current;

        public TestingBotDriver(ScenarioContext current)
        {
            this.current = current;
        }

        public AppiumDriver<AndroidElement> Init()
        {
            AppiumOptions appiumOptions = new AppiumOptions();
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.DeviceName, "Galaxy S23");
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.PlatformName, "Android");
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.PlatformVersion, "13.0");
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.App, "tb://...");

            String key = "TB_KEY";
            String secret = "TB_SECRET";

            appiumOptions.AddAdditionalCapability("key", key);
            appiumOptions.AddAdditionalCapability("secret", secret);
            appiumOptions.AddAdditionalCapability("realDevice", true);

            AppiumDriver<AndroidElement> driver = new AndroidDriver<AndroidElement>(
                new Uri("https://hub.testingbot.com/wd/hub"),
                appiumOptions
            );
            return driver;
        }

        public void Cleanup()
        {
            if (driver != null)
            {
                driver.Quit();
            }
        }
    }
}
Copy code
using System;
using OpenQA.Selenium;
using OpenQA.Selenium.Appium;
using OpenQA.Selenium.Appium.Android;
using OpenQA.Selenium.Appium.Enums;

namespace testingbot
{
    [Binding]
    public sealed class TestingBot
    {
        private TestingBotDriver tbDriver;

        [BeforeScenario]
        public void BeforeScenario()
        {
            tbDriver = new TestingBotDriver(ScenarioContext.Current);
            ScenarioContext.Current["tbDriver"] = tbDriver;
        }

        [AfterScenario]
        public void AfterScenario()
        {
            tbDriver.Cleanup();
        }
    }

    public class TestingBotDriver
    {
        private AppiumDriver<IOSElement> driver;
        private ScenarioContext current;

        public TestingBotDriver(ScenarioContext current)
        {
            this.current = current;
        }

        public AppiumDriver<IOSElement> Init()
        {
            AppiumOptions appiumOptions = new AppiumOptions();
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.DeviceName, "iPhone 15");
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.PlatformName, "iOS");
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.PlatformVersion, "18.0");
            appiumOptions.AddAdditionalCapability(MobileCapabilityType.App, "tb://...");

            String key = "TB_KEY";
            String secret = "TB_SECRET";

            appiumOptions.AddAdditionalCapability("key", key);
            appiumOptions.AddAdditionalCapability("secret", secret);
            appiumOptions.AddAdditionalCapability("realDevice", true);

            AppiumDriver<IOSElement> driver = new AndroidDriver<IOSElement>(
                new Uri("https://hub.testingbot.com/wd/hub"),
                appiumOptions
            );
            return driver;
        }

        public void Cleanup()
        {
            if (driver != null)
            {
                driver.Quit();
            }
        }
    }
}

Uploading Your App

Please see our Upload Mobile App documentation to find out how to upload your app to TestingBot for testing.

Specify Browsers & Devices

To run your existing tests on TestingBot, your tests will need to be configured to use the TestingBot remote machines. If the test was running on your local machine or network, you can simply change your existing test like this:

Before:
Copy code
IOSDriver<IOSElement> driver = new IOSDriver<IOSElement>(
    new Uri("http://localhost:4444/wd/hub"),
    appiumOptions
);
After:
Copy code
IOSDriver<IOSElement> driver = new IOSDriver<IOSElement>(
    new Uri("https://hub.testingbot.com/wd/hub"),
    appiumOptions
);

Configuring Capabilities

Capabilities are key-value pairs that allows you to customize your tests on TestingBot.
Appium provides its own set of capabilities which you can specify.
TestingBot also provide its own Custom Capabilities, to customize tests ran on the TestingBot platform.

You can use the drop-down menus below to see how to configure your tests to run on a specific mobile device:

1. Select a Device Type
2. Select a Device Name
Copy code

Testing Internal Websites

We've built TestingBot Tunnel, to provide you with a secure way to run tests against your staged/internal webapps.
Please see our TestingBot Tunnel documentation for more information about this easy to use tunneling solution.

The example below shows how to easily run a NUnit C# test with our Tunnel:

1. Download our tunnel and start the tunnel:

Copy code
java -jar testingbot-tunnel.jar key secret

2. Adjust your test: instead of pointing to 'hub.testingbot.com/wd/hub' like the example above - change it to point to your tunnel's IP address.
Assuming you run the tunnel on the same machine you run your tests, change to 'localhost:4445/wd/hub'. localhost is the machine running the tunnel, 4445 is the default port of the tunnel.

This way your test will go securely through the tunnel to TestingBot and back:

Copy code
using System;
using OpenQA.Selenium;
using OpenQA.Selenium.Remote;

namespace SeleniumTest {
  class Program {
    
    [Test]
    public void testLocal()
      driver.Navigate().GoToUrl("https://www.google.com/ncr");
      Console.WriteLine(driver.Title);

      AndroidElement query = driver.FindElement(By.Name("q"));
      query.SendKeys("TestingBot");
      query.Submit();
      Console.WriteLine(driver.Title);
    }
  }
}

Run tests in Parallel

Parallel Testing means running the same test, or multiple tests, simultaneously. This greatly reduces your total testing time.

You can run the same tests on all different browser configurations or run different tests all on the same browser configuration.
TestingBot has a large grid of machines and browsers, which means you can use our service to do efficient parallel testing. It is one of the key features we provide to greatly cut down on your total testing time.

Please see our PNUnit documentation for parallel testing.

Queuing

Every plan we provide comes with a limit of parallel tests.
If you exceed the number of parallel tests assigned to your account, TestingBot will queue the additional tests (for up to 6 minutes) and run the tests as soon as slots become available.

Mark tests as passed/failed

To see if a test passed or not in our member area, or to send additional meta-data to TestingBot, you can use our API.

Please see the example below on how to notify TestingBot about the test success state:

Copy code
[TearDown]
    public void CleanUp()
    {
        bool passed = TestContext.CurrentContext.Result.Status == TestStatus.Passed;
        try
        {
            // Logs the result to TestingBot
            ((IJavaScriptExecutor)driver).ExecuteScript("tb:test-result=" + (passed ? "passed" : "failed"));
        }
        finally
        {
            // Terminates the remote webdriver session
            driver.Quit();
        }
    }

Preparing your App

You do not need to install any code or plugin to run a test.
Below are some things that are necessary to successfully run a mobile test:

For Android:
  • Please supply the URL to your .apk or .aab file.
    Important: the .apk file needs to be a x86 build (x86 ABI) for Android emulators.
For iOS Real Device:
  • Please supply the URL to an .ipa file.
For iOS Simulator:
  • Please supply the URL to a .zip file that contains your .app
  • The .app needs to be an iOS Simulator build:
    • Create a Simulator build:
      Copy code
      xcodebuild -sdk iphonesimulator -configuration Debug
    • Zip the .app bundle:
      Copy code
      zip -r MyApp.zip MyApp.app

Additional Options

Appium provides a lot of options to configure your test.

Some important options that might help:

For Android:
  • appActivity and appPackage: by default, Appium will try to extract the main Activity from your apk. If this fails, you can supply your own with these options.
  • chromeOptions: additional chromedriver options you can supply.
  • otherApps: a JSON array of other apps that need to be installed, in URL format.
For Android & iOS:
  • locale: the language of the simulator/device (ex: fr_CA)
  • newCommandTimeout: How long (in seconds) Appium will wait for a new command from the client before assuming the client quit and ending the session