Steps needed to migrate from the App Center CLI

• This would apply in case you are using the CLI to trigger Appium tests on App Center
• You would need to first signup for a BrowserStack Account here
• Once you have signed up, you need to purchase a plan on BrowserStack. You can see all the plans here
• You can use App Automate’s SDK to migrate from the App Center to BrowserStack. It would be as simple as creating one configuration file to run all the tests on BrowserStack.
• You can read more about the App Automate’s SDK here
• The SDK is available in multiple Appium Frameworks like TestNG, Java, JUnit, NUnit, Python and many more. You can find documentation for each one of those frameworks here
• You would probably be using a CLI command like this - appcenter test run appium --app "APP_ID" --devices "DEVICE_SET_ID" --app-path PATH_TO_FILE.apk --test-series "main" --locale "en_US" --build-dir target/upload
• This CLI command has multiple parameters like APP_ID & DEVICE_SET_ID
• For each one of these CLI paramaters you can find an equivalent param for the SDK, you can find detailed notes on each param in the SDK over here
• All you would need to do would be to convert each one of the CLI params to SDK params and then trigger the tests on BrowserStack using the SDK

Steps needed to migrate from the Azure Pipelines App Center Task

• This would apply in case you are using the App Center Task for Azure Pipelines to trigger Appium tests on App Center
• You would need to first signup for a BrowserStack Account here
• Once you have signed up, you need to purchase a plan on BrowserStack. You can see all the plans here
• You can use App Automate’s Azure Pipelines Task/Plugin to migrate from the App Center to BrowserStack. It would be as simple as creating one configuration file to run all the tests on BrowserStack.
• You can read more about the App Automate’s Azure Task/Plugin here
• The Azure Piplines Task works with multiple Appium Frameworks like TestNG, Java, JUnit, NUnit, Python and many more.
• You can find a video of an example migration here
• Alternatively you can also use the SDK directly in your Azure Pipelines Task.

Further Troubleshooting

• There are certain Core Concepts in App Center defined here , for each one of these Core Concepts in App Center, there is one in BrowserStack. We are listing them down below
• The core concept of ‘Device Configuration’ in App Center is a combination of device model and operating system version. You can select the same and do much more (Use Regex) on BrowserStack. You can read more on that here
• Similar to how there are Device Tiers in App Center , there are Device Tiers in BrowserStack too , you can read more about them here
• The core concept of ‘Device Concurrency’ in App Center will map to the concept of Parallels in App Automate
• The core concept of ‘Test Run’ & ‘Test Report’ would equate to an Appium Session & it’s Reports on BrowserStack. You can see your Appium Sessions on either the Dashboard or you can use our API
• The core concept of ‘Test Series’ which is an arbitrary system for organizing your test runs, maps directly to the ‘Build Name’ param in BrowserStack’s SDK configuration. Also BrowserStack provides multiple other ways of organising your tests, you can read more on that here