Test runs

Test runs are an important component for tracking and managing the testing process. Our REST API provides comprehensive endpoints for handling test runs, enabling you to automate and streamline your testing workflow. With these endpoints, in a project, you can access list of test runs, create new test runs, and add test results to test runs.

Note: For a comprehensive list of default Enum values (such as Priority, State, and Type of Test Case), refer to the System-defined Enum values page.

Get test runs list

GET /api/v2/projects/{project_id}/test-runs

Invoking this API will fetch the list of test runs in a project associated with your username and access key. You will need the id of the project to access its list of test runs.

When requesting a list of test runs using the REST API, you can apply filters to get only the ones you want. Attributes-based filtering allows for selecting test cases by matching one or more attribute values passed as query parameters. The following table lists the available attributes.

API query name	Example value	Description
`closed_before`	date `YYYY-MM-DD` or `DD-MM-YYYY`	Only return test runs closed before this date.
`closed_after`	date `YYYY-MM-DD` or `DD-MM-YYYY`	Only return test runs closed after this date.
`created_before`	date `YYYY-MM-DD` or `DD-MM-YYYY`	Only return test runs created before this date.
`created_after`	date `YYYY-MM-DD` or `DD-MM-YYYY`	Only return test runs created after this date.
`test_plan_id`	string (e.g., `TP-1`)	Return all test runs linked to this test plan. (Only single values are allowed)
`assignee`	string (e.g., `john@email.com`)	Return all test runs assigned to this user. (Multiple values can be passed, comma-separated)
`include_closed`	Boolean (`true` or `false`)	Determines whether to include closed test runs in the response. `true` will include both active and closed test runs, while `false` will only include active test runs.
`run_state`	string (e.g., `new`)	Return all test runs with this state. (Multiple values can be passed, comma-separated). Possible values: `new`, `under_review`, `in_progress`, `rejected`, `done`, `closed`

When you provide multiple values for the same query parameter, any one value must match the specified attributes. This means that an OR operator is applied within the query parameter. On the other hand, if you include multiple attribute values across different parameters, an AND operator is used across these different parameters. This requires all conditions to be met for a match.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
https://test-management.browserstack.com/api/v2/projects/PR-1575/test-runs?run_state=rejected,closed&created_before=2024-11-01&closed_after=2024-11-15&test_plan_id=TP-1&assignee=abc@email.com

project_id^* String

Identifier of the project.

Response Attributes `200 OK` `json`

Response

{
  "success": true,
  "test_runs": [
    {
      "active_state": "active",
      "run_state": "done",
      "assignee": "john@email.com",
      "created_at": "2023-11-28T13:33:26.000Z",
      "identifier": "TR-78282",
      "name": "sample build #2",
      "project_id": "PR-1",
      "test_cases_count": 5,
      "configurations": [101, 102, 103],
      "include_closed": true
    }
  ]
}

active_state String

State of the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
assignee String

Email of the test run assignee.
created_at String

The time the test run was created on BrowserStack servers.
Identifier String

Identifier of the test run.
Show 4 more
name String

Name of the test run.
project_id String

Identifier of the project.
test_cases_count Integer

Count of number of test cases.
configurations Array

A list of unique identifiers, each specifying a distinct combination of operating system, browser, and device.

Create a test run

POST /api/v2/projects/{project_id}/test-runs

Invoking this API will create test runs programmatically, providing flexibility and automation in managing your test cycles. To create a test run, you will need the id of the project in which the test run should be created. If you need to link this test run to a test plan, you will require the id of that test plan.

You can apply filters to get only the test cases you want. Attributes-based filtering allows for selecting test cases by matching one or more attribute values passed as query parameters. When you provide multiple values for the same query parameter, any one value must match the specified attributes. This means that an OR operator applies within the query parameter. On the other hand, if you include multiple attribute values across different parameters, an AND operator is used across these different parameters. This requires all conditions to be met for a match.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST https://test-management.browserstack.com/api/v2/projects/PR-1/test-runs

project_id^* String

Identifier of the project.

Request Body

Request Body

{
  "test_run": {
    "name": "Test Run-29/11/2023",
    "description": "check the performance of the test run",
    "run_state": "new_run",
    "assignee": "john@email.com",
    "test_case_assignee": "john@email.com",
    "tags": [
      "Regression"
    ],
    "issues": ["TASK-309"],
    "issue_tracker": {
      "name": "jira",
      "host": "https://demo.atlassian.net"
    },
    "configurations": [101, 102, 103],
    "test_plan_id" : "TP-20",
    "test_cases": ["TC-1", "TC-3"],
    "folder_ids": [34, 54, 64],
    "include_all": false,
    "filter_test_cases": {
      "status": ["active", "draft"],
      "priority": ["medium","low" ],
      "case_type": ["regression", "smoke"],
      "owner": ["randomUser@email.com", "uniqueUser@email.com"],
      "tags": ["test", "regression"],
      "custom_fields": {
        "my_custom_field": ["sample_value_1", "sample_value_2"],
        "test": ["a1", "a2"],
        "estimate": [10, 20]
      }
    }
  }
}

name String

Name of the test run.
description String

Brief information about the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
assignee String

Email of the test run assignee.
test_case_assignee String

Email of the test case assignee.
Show 9 more
tags Array

Descriptive labels or keywords linked to the test run.
issues Array

List of the linked Jira, Asana or Azure issues.
issue_tracker Object

Ensures that issue IDs are correctly associated with their respective issue tracking tool, facilitating accurate linking and management.

▶ SHOW VALUES
- name String
  
  Specifies the issue tracking system to integrate with. For example, use jira for Jira, azure for Azure DevOps, or asana for Asana.
- host String
  
  The base URL of your issue tracking system. For Jira Cloud instances, this typically follows the format https://your-domain.atlassian.net.
configurations Array

A list of unique identifiers, each specifying a distinct combination of operating system, browser, and device. This optional parameter is required only if a test run includes configurations.
test_plan_id String

Identifier of the test plan.
test_cases Array

List of test case IDs.
folder_ids Array

Identifiers of each folder.
include_all Boolean

If the value is true, all test cases in the project are added to the test run.
filter_test_cases Object

Use this object if you want to filter test cases before appending to the test run.

▶ SHOW VALUES

Response Attributes `200 OK` `json`

Response

{
  "success": true,
  "testrun": {
      "active_state": "active",
      "run_state": "new_run",
      "created_at": "2023-11-29T06:26:22.215Z",
      "description": "check the performance of the test run",
      "identifier": "TR-78527",
      "name": "Test Run-29/11/2023",
      "assignee": "john@email.com",
      "project_id": "PR-1",
      "tags": ["performance"],
      "test_cases_count": 1,
      "updated_at": "2023-11-29T06:26:22.215Z",
      }
  }

success Boolean

API call is executed successfully.
active_state String

State of the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
created_at String

The time at which the test run was created on BrowserStack servers.
description String

Brief information about the test run.
Show 7 more
Identifier String

Identifier of the test run.
name String

Name of the test run.
assignee String

Email of the test run assignee.
project_id String

Identifier of the Project.
tags Array

Descriptive labels or keywords linked to the test run.
test_cases_count Integer

Count of number of test cases.
updated_at String

The time at which the test run was updated on BrowserStack servers.

Get test run details

GET /api/v2/projects/{project_id}/test-runs/{test_run_id}

Invoking this API will fetch the details of test cases linked to a test run. You will need the id of the project and id of the test run to access the details of test cases. The sample request has PR-1 and TR-78527 as placeholders representing project ID and test run ID, respectively.

This list is paginated; for more information, refer Pagination.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
https://test-management.browserstack.com/api/v2/projects/PR-1/test-runs/TR-78527

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Response Attributes `200 OK` `json`

Response

{
   "success":true,
   "test_run":{
      "active_state":"active",
      "run_state":"new_run",
      "created_at":"2023-11-29T06:26:22.215Z",
      "description":"",
      "identifier":"TR-78527",
      "name":"Test Run-29/11/2023",
      "assignee":"john@email.com",
      "project_id":"PR-1",
      "configurations":[101, 102, 103],
      "test_cases":[
         {
            "assignee":"john@email.com",
            "case_type":"other",
            "priority":"High",
            "status":"Active",
            "description":"",
            "identifier":"TC-1",
            "name":"Assign tags to user and then re-open the modal",
            "latest_status":"Passed",
            "configuration_id":101,
            "latest_result_id":108767
         }
      ],
      "links":{
         "test_cases":"/api/v2/projects/PR-1/test-runs/TR-78527/test-cases"
      },
      "tags":["ttt"],
      "test_cases_count":3,
      "updated_at":"2023-11-29T06:26:22.215Z",
      "passed_count":1,
      "failed_count":1,
      "customstatus_count":1,
      "overall_progress":{
         "untested":0,
         "passed":2,
         "retest":0,
         "failed":0,
         "blocked":0,
         "skipped":0,
         "in_progress":0
      }
   }
}

active_state String

State of the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
created_at String

The time the test run was created on BrowserStack servers.
description String

Brief information about the test run.
Identifier String

Identifier of the test run.
Show 9 more
name String

Name of the test run.
assignee String

Email of the test run assignee.
project_id String

Identifier of the project.
configurations Array

A list of unique identifiers, each specifying a distinct combination of operating system, browser, and device.
test_cases Array

This list has information about a specific test case.

▶ SHOW VALUES
- assignee String
  
  Email of the test run assignee.
- case_type String
  
  Gives the type of test case.
- priority String
  
  Gives the priority of the test case.
- status String
  
  Gives the state of the test case.
- description String
  
  Brief information about the test case.
- name String
  
  Gives the title of the test case.
- latest_status String
  
  Gives the status of the test case.
- latest_result_id integer
  
  The latest result id of the test case in the run.
- configuration_id Integer
  
  Unique identifier for a specific operating system, browser, and device configuration.
links String

Give the api endpoint url of the test case.
tags Array

Descriptive labels or keywords linked to the test case.
test_cases_count Object

Count of number of test cases.
overall_progress Object

This object provides a comprehensive summary of the test run’s overall status, including both system status (such as passed and failed) and any user-defined custom statuses.

Get test run details minified

GET /api/v2/projects/PR-1/test-runs/TR-5/test-cases?minify=true

This endpoint returns minified details for a specific test run. The response contains only essential fields for the test run, making it suitable for scenarios where you need a lightweight payload (for example, quick status checks or summary views).

Request parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
https://test-management.browserstack.com/api/v2/projects/PR-75/test-runs/TR-152?minify=true

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Response attributes `200 OK` `json`

Response

{
   "success":true,
   "test_run":{
      "active_state":"active",
      "run_state":"new_run",
      "created_at":"2025-08-20T10:27:03.000Z",
      "updated_at":"2025-08-20T10:27:03.000Z",
      "description":"",
      "identifier":"TR-152",
      "name":"Test Run-20/08/2025",
      "assignee":"user@email.com",
      "project_id":"PR-75",
      "overall_progress":{
         
      },
      "tags":[
         
      ],
      "configurations":[
         
      ],
      "links":{
         "self":"/api/v1/projects/10075/test-runs/TR-152",
         "test_cases":"/api/v2/projects/PR-75/test-runs/TR-152/test-cases"
      }
   }
}

success Boolean

Indicates if the request was successful.
test_run Object

The test run object containing minified details.

▶ SHOW VALUES
- active_state String
  
  State of the test run.
- run_state String
  
  State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
- created_at String
  
  The time the test run was created on BrowserStack servers.
- updated_at String
  
  The time the test run was last updated on BrowserStack servers.
- description String
  
  Brief information about the test run.
- identifier String
  
  Unique identifier of the test run.
- name String
  
  Name of the test run.
- assignee String
  
  Email of the test run assignee.
- project_id String
  
  Unique identifier of the project.
- overall_progress Object
  
  This object provides a comprehensive summary of the test run’s overall status, including both system status (such as passed and failed) and any user-defined custom statuses.
- tags Array
  
  Descriptive labels or keywords linked to the test run.
- configurations Array
  
  A list of unique identifiers, each specifying a distinct combination of operating system, browser, and device.
- links Object
  
  API endpoint URLs related to the test run, such as self and test_cases.

Get test cases of a test run

GET /api/v2/projects/{project_id}/test-runs/{test_run_id}/test-cases

Invoking this API will fetch the details of all the test cases linked to a test run. You will need the id of the project and id of the test run to access the details of test cases. Using this endpoint, you can retrieve the first thirty test cases. This list is paginated; for more information, refer Pagination.

The sample request has PR-1 and TR-78527 as placeholders representing project ID and test run ID, respectively.
Use fetch_steps query parameter in the API to get test case steps. When the fetch_steps query parameter is used, the API returns the first 30 test case steps. Pagination is not supported for requests that include this parameter. The steps array is populated with step objects, each containing its own id and order.

Example: https://test-management.browserstack.com/api/v2/projects/PR-1/test-runs/TR-78527/test-cases?fetch_steps=true

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
https://test-management.browserstack.com/api/v2/projects/PR-1/test-runs/TR-78527/test-cases?p=1

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Response Attributes `200 OK` `json`

Response

{
   "success":true,
   "info":{
      "page":1,
      "page_size":30,
      "count":94,
      "prev":null,
      "next":2
   },
   "test_cases":[
      {
         "case_type":"Destructive",
         "priority":"High",
         "status":"Active",
         "description":"Subject the password reset system to sustained high load over an extended period and monitor for any degradation in performance or stability issues. This test is important to ensure the system can maintain performance during extended periods of high usage.",
         "identifier":"TC-972133",
         "name":"Verify system stability during prolonged high load",
         "steps":[
            {
               "id":34001057,
               "order":1,
               "description":"Initiate a high-load scenario using the load testing tool, simulating a consistently high number of password reset requests over an extended period (e.g., 24 hours).",
               "result":"The system should accept and process reset requests consistently throughout the test period without significant degradation in performance."
            },
            {
               "id":34001061,
               "order":5,
               "description":"Regularly check the email sending process, measuring the time to generate, queue, and send recovery emails throughout the test period.",
               "result":"Email processing should keep pace with incoming requests, maintaining consistent performance (e.g., < 1 minute from request to email sent) throughout the test."
            }
         ],
         "latest_status":"untested",
         "latest_result_id":null,
         "assignee":null,
         "folder_path":[
            10456816
         ],
        "created_at": "2025-09-03T11:20:52.000Z",
        "last_updated_at": "2025-09-03T11:29:34.000Z",
        "created_by": "user1@email.com",
        "last_updated_by": "user2@email.com",
      }
   ]
}

success Boolean

API call is executed successfully.
info Object

Additional pagination information.

▶ SHOW VALUES
- page Integer
  
  The current page being viewed displays a list of test cases.
- page_size Integer
  
  Number of test cases in the page.
- count Integer
  
  Total number of records across all pages.
- prev Integer
  
  Previous page number.
- next Integer
  
  Next page number.
test_cases Array

This list has information about a specific test case.

▶ SHOW VALUES
- case_type String
  
  Gives the type of test case.
- priority String
  
  Gives the priority of the test case.
- status String
  
  Gives the state of the test case.
- description String
  
  Brief information about the test case.
- identifier String
  
  Unique identifier of the test case.
- name String
  
  Gives the title of the test case.
- steps Array
  
  List of step objects for the test case, each representing an individual action and expected result.
- latest_status String
  
  Gives the status of the test case.
- latest_result_id String
  
  Gives the ID of the latest test result.
- assignee String
  
  Email of the test run assignee.
- folder_path Array
  
  It is a list of test case folder IDs, starting with the root folder at the top and ending with the last folder at the bottom.
- created_at String
  
  Timestamp (ISO 8601) when the test case was created.
- last_updated_at String
  
  Timestamp (ISO 8601) when the test case was last updated.
- created_by String
  
  Email of the user who created the test case.
- last_updated_by String
  
  Email of the user who last updated the test case.

Get test cases of a test run minified

GET /api/v2/projects/PR-75/test-runs/TR-152?minify=true

Invoking this API fetches only the essential fields of all the test cases linked to a test run, such as test case ID, description, title and the latest status. You will need the id of the project and id of the test run to access the details of test cases.

Request parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
https://test-management.browserstack.com/api/v2/projects/PR-1/test-runs/TR-5/test-cases?minify=true

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Response attributes `200 OK` `json`

Response

{
   "success":true,
   "info":{
      "page":1,
      "page_size":30,
      "count":1,
      "prev":null,
      "next":null
   },
   "test_cases":[
      {
         "description":"WINDOWS,Unknown - Edge,110",
         "identifier":"TC-98",
         "name":"Check whether the application has secure protocols like HTTPS.",
         "latest_status":"untested"
      }
   ]
}

success Boolean

API call is executed successfully.
info Object

Additional pagination information.

▶ SHOW VALUES
- page Integer
  
  The current page being viewed displays a list of test cases.
- page_size Integer
  
  Number of test cases in the page.
- count Integer
  
  Total number of records across all pages.
- prev Integer
  
  Previous page number.
- next Integer
  
  Next page number.
test_cases Array

List of minified test case objects for the test run.

▶ SHOW VALUES
- description String
  
  Brief information about the test case, such as configuration or environment.
- identifier String
  
  Unique identifier of the test case.
- name String
  
  Name of the test case.
- latest_status String
  
  The most recent status of the test case in the test run.

Update a test run (PATCH)

PATCH /api/v2/projects/{project_id}/test-runs/{test_run_id}/update

Use this API to update an existing test run. Unlike the POST method which requires all fields to be present, this PATCH endpoint only updates the fields that are provided in the request body. This allows for partial updates to a test run without needing to resend all the data. To update a test run, you will need both the id of the project (eg: PR-2134) and the id of the test run (eg: TR-2343) within that project.

Note:

To clear an array field (like tags or issues), you must send an empty array ([]) in the request body.

Omitting a field from the request body will leave that field unchanged.

The PATCH API endpoint is used to update specific fields. Include only the fields you wish to modify in the request body.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X PATCH https://test-management.browserstack.com/api/v2/projects/{project_id}/test-runs/{test_run_id}/update

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Request Body

Request Body

{
  "test_run": {
    "name": "Test Run-29/11/2023",
    "run_state": "new",
    "tags": ["ttt"],
    "filter_test_cases": {
      "status": ["active", "draft"],
      "priority": ["medium","low" ],
      "case_type": ["regression", "smoke"],
      "owner": ["randomUser@email.com", "uniqueUser@email.com"],
      "tags": ["test", "regression"]
  }
}

name String

Name of the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
tags Array

Descriptive labels or keywords linked to the test run.
filter_test_cases Object

Use this object if you want to filter test cases before appending to the test run.

▶ SHOW VALUES
- status Array
  
  Indicates the status of the test case.
- priority Array
  
  Priority of the test case.
- case_type Array
  
  Type of test case.
- owner Array
  
  Email of the owner of test case.
- tags Array
  
  Descriptive labels or keywords linked to the test case.

Response Attributes `200 OK` `json`

Response

{
  "success": true,
  "testrun": {
    "name": "Test Run-29/11/2023",
    "run_state": "new",
    "tags": ["ttt"]
  }
}

success Boolean

API call is executed successfully.
name String

Name of the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
tags Array

Descriptive labels or keywords linked to the test run.

Update a test run (POST)

POST /api/v2/projects/{project_id}/test-runs/{test_run_id}/update

Invoking this API allows you to update test runs in a given project. When you update the test run, the new test cases in the update test run request will replace all the existing test cases. To update a test run, you will need both the id of the project (eg: PR-2134) and the id of the test run (eg: TR-2343) within that project.

Note: The POST API endpoint requires a complete request body. All listed parameters must be included in your Request Body, even if they have null or default values.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST https://test-management.browserstack.com/api/v2/projects/{project_id}/test-runs/{test_run_id}/update

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Request Body

Request Body

{
  "test_run": {
    "name": "Test Run-29/11/2023",
    "description": "gas",
    "run_state": "new_run",
    "assignee": "john@email.com",
    "test_case_assignee": "john@email.com"
    "tags": [
      "ttt"
    ],
    "issues": [
      "XYZ-1"
    ],
    "issue_tracker": {
      "name": "jira",
      "host": "https://demo.atlassian.net"
    },
    "test_plan_id" : "TP-20",
    "configurations": [101, 102],
    "test_cases": ["TC-1", "TC-3"],
    "folder_ids": [34,54,64],
    "filter_test_cases": {
      "status": ["active", "draft"],
      "priority": ["medium","low" ],
      "case_type": ["regression", "smoke"],
      "owner": ["randomUser@email.com", "uniqueUser@email.com"],
      "tags": ["test", "regression"]
  }
}

name^* String

Name of the test run.
description^* String

Brief information about the test run.
run_state^* String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
assignee^* String

Email of the test run assignee.
test_case_assignee^* String

Email of the test case assignee.
Show 8 more
tags^* Array

Descriptive labels or keywords linked to the test run.
issues^* Array

List of the linked Jira, Asana or Azure issues.
issue_tracker Object

Ensures that issue IDs are correctly associated with their respective issue tracking tool, facilitating accurate linking and management.

▶ SHOW VALUES
- name String
  
  Specifies the issue tracking system to integrate with. For example, use jira for Jira, azure for Azure DevOps, or asana for Asana.
- host String
  
  The base URL of your issue tracking system. For Jira Cloud instances, this typically follows the format https://your-domain.atlassian.net.
test_plan_id^* String

Identifier of the test plan.
configurations^* Array

A list of unique identifiers, each specifying a distinct combination of operating system, browser, and device. This optional parameter is required only if a test run includes configurations.
test_cases^* Array

List of test case IDs.
folder_ids^* Array

Identifiers of each folder.
filter_test_cases Object

Use this object if you want to filter test cases before appending to the test run.

▶ SHOW VALUES
- status Array
  
  Indicates the status of the test case.
- priority Array
  
  Priority of the test case.
- case_type Array
  
  Type of test case.
- owner Array
  
  Email of the owner of test case.
- tags Array
  
  Descriptive labels or keywords linked to the test case.

Response Attributes `200 OK` `json`

Response

{
  "success": true,
  "testrun": {
    "active_state": "active",
    "run_state": "new_run",
    "created_at": "2023-11-29T06:26:22.215Z",
    "description": "gas",
    "identifier": "TR-78527",
    "name": "Test Run-29/11/2023",
    "assignee": "john@email.com",
    "project_id": "PR-1",
    "test_plan": {
      "identifier": "TP-20",
      "name": "Test plan6"
    },
    "tags": [
      "ttt"
    ],
    "issues": [
      "XYZ-1"
    ],
    "test_cases_count": 2,
    "updated_at": "2023-11-29T06:26:22.215Z"
  }
}

success Boolean

API call is executed successfully.
active_state String

State of the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
created_at String

The time at which the test run was created on BrowserStack servers.
description String

Brief information about the test run.
Show 9 more
Identifier String

Identifier of the test run.
name String

Name of the test run.
assignee String

Email of the test run assignee.
project_id String

Identifier of the Project.
test_plan JSON Object

This list has information about a specific test plan.

▶ SHOW VALUES
tags Array

Descriptive labels or keywords linked to the test run.
issues Array

List of the linked Jira, Asana or Azure issues.
test_cases_count Integer

Count of number of test cases.
updated_at String

The time at which the test run was updated on BrowserStack servers.

Update assignee of test cases within a test run

POST /api/v2/projects/PR-5512/test-runs/TR-126509/assign

Invoking this API will update assignees of test cases within a test run. To do so, you will need the id of the project, the id of the test run (eg: TR-2343), the id of test cases, and the email of assignees.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST https://test-management.browserstack.com/api/v2/projects/PR-5512/test-runs/TR-126509/assign

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Request Body

Request Body

{
  "assign_to": [
    {
      "test_case_id": "TC-337204",
      "configuration_id": 2,
      "assignee": "john@email.com"
    },
    {
      "test_case_id": "TC-337205",
      "configuration_id": 1,
      "assignee": "randomUser@email.com"
    },
    {
      "test_case_id": "TC-337203",
      "configuration_id": 1,
      "assignee": "uniqueUser@email.com"
    }
  ]
}

test_case_id^* String

Test case ID whose assignee should be updated.
configuration_id Integer

Unique identifier for a specific operating system, browser, and device configuration. This optional parameter is required only if a test run includes configurations.
assignee^* String

Email of the assignee.

Response Attributes `200 OK` `json`

Response

{
    "success": true
}

success Boolean

API call is executed successfully.

Close a test run

POST /api/v2/projects/{project_id}/test-runs/{test_run_id}/close

Invoking this API will close test runs in a given project. To close a test run, you will need the id of test run and id of the project in which the test run exists.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST https://test-management.browserstack.com/api/v2/projects/PR-13/test-runs/TR-128/close

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Response Attributes `200 OK` `json`

Response

{
  "success": true,
  "testrun": {
    "active_state": "closed",
    "run_state": "closed",
    "created_at": "2023-12-21T09:03:10.000Z",
    "description": "Login functionality under user load",
    "identifier": "TR-128",
    "name": "Test Run-05/12/2023",
    "assignee": "john@email.com",
    "project_id": "PR-13",
    "test_cases_count": 0
  }
}

active_state String

State of the test run.
run_state String

State of the test run. The valid states are new_run, in_progress, under_review, rejected, done, and closed.
created_at String

The time the test run was created on BrowserStack servers.
description String

Brief information about the test run.
Identifier String

Identifier of the test run.
Show 4 more
name String

Name of the test run.
owner String

Email of the test run owner.
project_id String

Identifier of the project.
test_cases_count Integer

Count of number of test cases.

Delete a test run

POST /api/v2/projects/{project_id}/test-runs/{test_run_id}/delete

Invoking this API will delete a test run. You will need the id of the project and id of the test run to delete a test run.

Request Parameters

Request

curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
-X POST https://test-management.browserstack.com/api/v2/projects/PR-1/test-runs/TR-1234/delete

project_id^* String

Identifier of the project.
test_run_id^* String

Identifier of the test run.

Response Attributes `200 OK` `json`

Response

{
    "success": true,
    "message": "Test Run TR-1234 has been deleted successfully"
}

success Boolean

API call is executed successfully.
message String

Gives the information about the performed action.

Did this page help you?

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

This page has exactly what I am looking for
This content & code samples are accurate and up-to-date
The content on this page is easy to understand
Other (please tell us more below)

Any additional feedback?

Thank you for your valuable feedback

Test runs

Get test runs list

Request Parameters

project_id* String

Response Attributes 200 OK json

active_state String

run_state String

assignee String

created_at String

Identifier String

name String

project_id String

test_cases_count Integer

configurations Array

Create a test run

Request Parameters

project_id* String

Request Body

name String

description String

run_state String

assignee String

test_case_assignee String

tags Array

issues Array

issue_tracker Object

name String

host String

configurations Array

test_plan_id String

test_cases Array

folder_ids Array

include_all Boolean

filter_test_cases Object

Response Attributes 200 OK json

success Boolean

active_state String

run_state String

created_at String

description String

Identifier String

name String

assignee String

project_id String

tags Array

test_cases_count Integer

updated_at String

Get test run details

Request Parameters

project_id* String

test_run_id* String

Response Attributes 200 OK json

active_state String

run_state String

created_at String

description String

Identifier String

name String

assignee String

project_id String

configurations Array

test_cases Array

assignee String

case_type String

priority String

status String

description String

name String

latest_status String

latest_result_id integer

configuration_id Integer

links String

tags Array

test_cases_count Object

overall_progress Object

Get test run details minified

Request parameters

project_id* String

test_run_id* String

Response attributes 200 OK json

project_id^* String

Response Attributes `200 OK` `json`

project_id^* String

Response Attributes `200 OK` `json`

project_id^* String

test_run_id^* String

Response Attributes `200 OK` `json`

project_id^* String

test_run_id^* String

Response attributes `200 OK` `json`

project_id^* String

test_run_id^* String

Response Attributes `200 OK` `json`

project_id^* String

test_run_id^* String

Response attributes `200 OK` `json`

project_id^* String

test_run_id^* String