Copy entities across projects

Copy tests, datasets, and modules across BrowserStack Low Code Automation projects instead of recording them again.

Copy tests, datasets, and modules, along with their dependent entities, from one project to another to reuse them instead of rebuilding from scratch.

You can copy the following entities across projects:

• Tests
• Test datasets
• Modules

Copy tests

You can copy one or more tests, along with their dependent entities, from a source project to a destination project. You can select up to a maximum of 50 tests at a time.

Copy a single test

Copy one test to a destination project and folder of your choice.

Copy multiple tests

Select multiple tests at once and copy them to the destination project in a single operation.

For details on how BrowserStack handles a test’s dependent entities, see Dependent entity behavior.

Copy test datasets

You can copy a dataset independently of a test:

• Copy one or more datasets from one project to another, or within the same project.
• If the dataset is derived from a database connection, BrowserStack also copies the connection.

Copy a single dataset

Copy one dataset to a destination project of your choice.

Copy multiple datasets

Select multiple datasets at once and copy them to the destination project.

Copy modules

You can copy a module independently of a test:

• Copy one or more modules from one project to another, or within the same project.
• Copying a module creates a clone. BrowserStack doesn’t automatically map the copy to any existing tests, in the same project or a different one.
• If the module contains local, global, dataset, or secret variables, BrowserStack handles them the same way as described in Dependent entity behavior.

Copy a single module

Copy one module to a destination project of your choice.

Copy multiple modules

Select multiple modules at once and copy them to the destination project in a single operation, up to a maximum limit. The default limit is 50 modules.

Dependent entity behavior

When you copy an entity, BrowserStack also copies or maps its dependent entities. The following sections describe how each type of entity behaves.

Steps and configurations

BrowserStack copies all test steps, including validations, along with their configurations, such as timeout, override locators, configured attributes, failure logic, visual testing, input, and step images, to the new test as is.

Visual testing

BrowserStack copies all visual validation steps, along with their difference thresholds and visual testing configuration, to the new test as is. It copies only the source test’s initial baseline, and warns you if that baseline is too old.

Variables and secrets

BrowserStack handles variables and secrets based on whether they already exist in the destination project:

Datasets, connections, and modules

If a matching entity already exists in the destination project, the test uses it. Otherwise, BrowserStack creates a copy.

Copies follow two more rules:

• If a test, dataset, or module name is already taken, BrowserStack appends a numeric suffix, such as _1 or _2, using the last active number for that entity type plus one.
• If multiple selected tests share one module, BrowserStack creates a single copy and links all those tests to it.

Test organization and metadata

BrowserStack updates the following organizational and metadata entities in the destination project:

Points to remember

• You can run only one copy operation at a time. If you start another copy while one is in progress, BrowserStack queues it and starts it after the current copy completes.
• Multiple users can copy entities in the same project at the same time.

Related topics

• Projects
• Folders
• Data driven testing
• Modules
• Global variables
• Manage secrets