Run your first test
XCTestPlans helps us manage Unit/UI tests using XCode with multiple configurations and settings. To test XCTestPlan on Browserstack, the process is different from that of running XCUI Tests. BrowserStack App Automate supports XCTestPlans on a wide range of real iOS devices. This guide will help you run your first XCTestPlan on BrowserStack.
1. Setup
- You will need a BrowserStack
username
andaccess-key
. To obtain your access credentials, sign up for a free trial or purchase a plan.
2. Upload your app
Upload your iOS app (.ipa
) file to BrowserStack servers using a REST API request.
The following sample cURL command shows how to upload an app:
curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST "https://api-cloud.browserstack.com/app-automate/xcuitest/v2/app" \
-F "file=@/path/to/app/file/app-debug.ipa"
A sample response for the request is as follows:
{
"app_name":"app-debug.ipa",
"app_url":"bs://j3c874f21852ba57957a3fdc33f47514288c4ba4",
"app_version":"1.0",
"app_id":"j3c874f21852ba57957a3fdc33f47514288c4ba4",
"uploaded_at":"2022-05-13 06:16:49 UTC",
"expiry":"2022-06-12 06:16:49 UTC"
}
The value of the app_url
parameter in the response is used to specify the application under test when you run XCTestPlan.
3. Upload your test suite and xctestrun file
Upload your test suite .app
file and .xctestrun
file bundled together as a .zip
file to BrowserStack servers using a REST API request.
The following sample cURL command shows how to upload a test suite:
curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST "https://api-cloud.browserstack.com/app-automate/xcuitest/v2/test-suite" \
-F "file=@/path/to/test-suite/file/and/xctestrun/file/SampleXCTestPlan.zip"
A sample response for the request is as follows:
{
"test_suite_name":"SampleXCTestPlan.zip",
"test_suite_url":"bs://f7c874f21852ba57957a3fdc33f47514288c4ba4",
"test_suite_id":"f7c874f21852ba57957a3fdc33f47514288c4ba4",
"uploaded_at":"2022-05-13 06:17:50 UTC",
"expiry":"2022-06-12 06:17:50 UTC",
"framework":"xcuitest"
}
The value of the test_suite_url
parameter in the response is used to specify the test suite when you run XCTestPlan.
-
.xctestrun
file is generated when your Xcode project is built. The file can be found under{Derived_Directory}/Build/Products
- To know the location of your derivedDatadirectory, visit
Xcode → Preferences → Locations
. - Please bundle this along with your
<AppnameUITests>-Runner.app
found in the debug folder under{Derived_Directory}/Build/Products/Debug_{iOS device&version}
- Select the two files simultaneously and compress them to a
.zip
file.
The file structure of your zipped file can be visually represented as below:
├── `testSuite.zip`
└── test suite runner `.app` file
└── `.xctestrun` file
4. Execute XCUI tests
After you upload the app and test suite to BrowserStack servers, send an API request to start the test execution as shown in the following sample cURL request:
A sample response for the request is as follows:
{
"message":"Success",
"build_id":"4d2b4deb810af077d5aed98f479bfdd2e64f36c3"
}
The build_id
is used to uniquely identify your build in App Automate.
5. View test results
After you start the test-suite execution using the REST API request, visit your App Automate dashboard to view your test results, debugging logs, and overall test details. You can also use API requests to view test results.
Related topics
-
Manage your uploaded app or test suite using our upload app REST API and upload test suite REST API.
-
Use the get app API endpoint and list test suites API endpoint to list your recently uploaded apps and test suites.
-
Delete your uploaded app or test suite using the delete app API endpoint and delete test suite API endpoint.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!