Xamarin Test Cloud task
TFS 2017 | TFS 2015
This task was used in a build or release pipeline to test mobile apps with Xamarin Test Cloud using Xamarin.UITest
Note
This task is deprecated. Use the App Center Test task instead. Sign up with App Center first.
Demands
None
Arguments
| Argument | Description |
|---|---|
| App File | - If you want to test a single app, choose ... and select the .apk file. - If you want to test multiple apps, specify a match pattern filter. You can use a single-folder wildcard ( *) and recursive wildcards (**). For example, **/*.apk searches for all .apk files in all subdirectories. |
| dSYM File | To make crash logs easier to read, upload a .dSYM file that is associated with your app. Specify a path relative to the .ipa file. You can use a match pattern filter. For example: *.dSYMNote: This argument applies only to iOS apps. |
| Team API Key | Your Xamarin Test Cloud Team API key. To get it, go to your Xamarin Test Cloud account, and then to Teams & Apps. Important: Use a secret variable to avoid exposing this value. |
| User Email | Email address of your Xamarin Test Cloud account. |
| Devices | The devices string generated by Xamarin Test Cloud. To get this string: - Go to your Xamarin Test Cloud account. - Choose New Test Run. - Step through the wizard. - When you reach the final page, copy the ID that follows the --devices option. |
| Series | Series name for the test run. For example, master, production, or beta. See Xamarin: Creating A Test Run for a Team. |
| Test Assembly Directory | Relative path to the folder that contains the test assemblies. For example: SolutionName/TestsProjectName/bin/Release. |
| Advanced - Parallelization | Select None, By test fixture, or By test method. |
| Advanced - System Language | Select your language. If it isn't displayed, select Other and then enter its locale below. For example: en_AU. |
| Advanced - test-cloud.exe Location | Location of test-cloud.exe. In most cases leave this set to the default value. |
| Advanced - Optional Arguments | (Optional) Arguments passed to test-cloud.exe. See Submitting UITests at the Command Line. |
| Advanced - Publish results to VSO/TFS | Select if you want to pass the --nunit-xml option to test-cloud.exe so that results from the NUnit xml file are be published to TFS or Azure Pipelines. |
| Control options | See Control options |
Example
Open source
This task is open source on GitHub. Feedback and contributions are welcome.
FAQ
How do I add a Xamarin UITest to my solution?
Adding Xamarin.UITest to a Solution
Where can I learn more about file matching patterns?
File matching patterns reference
Do I need an agent?
You need at least one agent to run your build or release.
I'm having problems. How can I troubleshoot them?
See Troubleshoot Build and Release.
I can't select a default agent pool and I can't queue my build or release. How do I fix this?
See Agent pools.
My NuGet push task is failing with the following error: "Error: unable to get local issuer certificate". How can I fix this?
This can be fixed by adding a trusted root certificate. You can either add the NODE_EXTRA_CA_CERTS=file environment variable to your build agent, or you can add the NODE.EXTRA.CA.CERTS=file task variable in your pipeline. See Node.js documentation for more details about this variable. See Set variables in a pipeline for instructions on setting a variable in your pipeline.
I use TFS on-premises and I don't see some of these features. Why not?
Some of these features are available only on Azure Pipelines and not yet available on-premises. Some features are available on-premises if you have upgraded to the latest version of TFS.