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

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.

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.

Related topics

• Manage your uploaded apps/test packages using our REST API (Android/iOS).

• Delete your uploaded apps/test packages using the delete API endpoint (Android/iOS).