Skip to main content
Folders group the tests in your library. They form a tree: every folder has a parentId, which is null at the top level, and a folder can hold both tests and other folders. A folder is a label on a test, not a container that owns it. A test belongs to exactly one folder (or none), and deleting a folder never deletes a test.
Folders apply to the MobileBoost Platform test library. On a QA Studio organisation these endpoints answer 400, and folderId is refused on POST/PATCH /tests.
All requests below authenticate with your mb_live_ API key passed as a Bearer token in the Authorization header.

See the tree

GET /tests/folders returns every folder with its full path and how many tests are in it, counting subfolders, so one call is enough to find the folder you want:
testCount counts subfolders too: the four tests in Payments are part of the twelve in Checkout.

Create and nest folders

Names are for people to read, up to 60 characters. Two folders may share a name — everything that refers to a folder uses its id.

Rename and move

PATCH /tests/folders renames a folder, moves it, or both in one call. parentId: null moves it back to the top level; omitting parentId leaves it where it is.
Moving a folder takes its subfolders and its tests with it. Moving one inside its own subtree is refused with a 400, because that would detach the subtree from the tree.

File tests into a folder

1

Create a test directly into one

2

Move one test

folderId: null takes the test out of its folder. Omitting the field leaves the folder as it is.
3

Move many at once

Ids that no longer exist come back under skippedTestIds rather than failing the call, and a test already in that folder comes back under unchangedTestIds.
Changing a test’s folder never re-triggers automation generation: it does not change what the test should do.

List the tests in a folder

Without includeSubfolders, you get only the tests filed directly in that folder.

Delete a folder

Deleting a folder deletes no test. Its subfolders move up to its own parent, its tests become unfiled, and the response says exactly which:
To delete the tests as well, call DELETE /tests with their ids first.

Platform MCP server

The same folder operations as tools your coding agent can call.