Skip to main content
Transform your testing process with: Real Device Features, Company-wide Licences, & App Percy

Organize tests

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 to the following build API:

POST /app-automate/flutter-integration-tests/v2/android/build

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 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.

Tip: 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.

Example cURL requests for test executions:

In the following test executions, we 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.

Terminal
Copy icon Copy snippet
Terminal
Copy icon Copy snippet

FlutterProject—Name

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.

Example cURL request for adding build tag:

In the API request below, we set the the buildTag to Laser tag.

Terminal
Copy icon Copy snippet

Flutter-Build-Name

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

Is this page helping you?

Yes
No

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!

Talk to an Expert
Download Copy