Join our Discord
Organize your Flutter integration tests
Organize your Flutter test executions under projects on BrowserStack App Automate.
BrowserStack enables you to organize your tests using the following parameters:
-
project: Logically group multiple Flutter test executions. -
buildTag: Create custom tags for your test builds.
Both project and buildTag are optional parameters.
When you use these parameters in your build API call, their values are available as filters on the App Automate dashboard, as you’ll see later on this page. You can then use the values to filter your results.
Also, you can use the project parameter in your list recent builds API (Android or iOS) call to get a filtered list of builds.
Group tests under projects
To group your test executions under a specific project, include the project parameter in the build API request.
| Parameter | Description | Data type | Value |
|---|---|---|---|
project |
A unique identifier to logically group multiple test executions together | String | Letters (A-Z, a-z), digits (0-9), periods (.), colons (:), hyphens (-), square brackets ([]), forward slashes (/), asperands (@), ampersands (&), single quotes (‘), and underscores (_) are allowed. Any other characters are ignored. |
Additionally, you can set the projectNotifyURL parameter with the project parameter to specify a callback URL. This parameter enables BrowserStack to notify you all builds under the given project are completed. You receive a callback, if no new builds triggered for 5 mins and all existing builds have finished execution. For more information, refer to Execute builds API Android or iOS.
Example cURL requests for test executions:
In the following test executions, you specify the same value Dashboard-v2 for the project parameter. As a result, the name Dashboard-V2 is associated with the two builds.
Then, use the Dashboard-V2 filter on the App Automate dashboard to group the results of these executions.
Organize tests using build tags
Another way to organize your tests on the App Automate dashboard is by setting a custom build tag in your build API call. Use the buildTag parameter to set it. For example, you might need to classify your builds based on unique factors such as release version, test environment, or git branch. In these cases, you can use separate build tags as parameters. After your tests have run, you can filter them on the dashboard using your build tag.
| Parameter | Description | Data type | Value |
|---|---|---|---|
buildTag |
A custom tag for your builds | String | Letters (A-Z, a-z), digits (0-9), periods (.), colons (:), hyphens (-), square brackets ([]), forward slashes (/), asperands (@), ampersands (&), single quotes (‘), and underscores (_) are allowed. Any other characters are ignored. |
To add a build tag, set a build name first. Without a build name, build tags are ignored.
Example cURL request for adding build tag:
In the API request below, you set the buildTag to Laser tag.
Related topics
-
Manage your uploaded apps or test packages using our REST API (Android or iOS).
-
Delete your uploaded apps or test packages using the delete API endpoint (Android or iOS).
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!