The Bulk Actions menu on the Test Listing page lets you manage multiple test cases at once, whether you’re running, organizing, or moving them across projects or accounts.
What You Can Do with Bulk Actions
- Run Tests – Execute tests across all enabled browsers at once.
- Run on Browser – Limit execution to specific browsers.
- Stop Tests – Interrupt any currently running tests.
- Delete – Permanently delete the selected tests.
- Activate / Deactivate – Toggle tests on or off when moving across environments or to prevent accidental execution.
- Enable All Browsers – Quickly enable new browsers added to a project.
- Change Schedule – Adjust when tests run (on demand, hourly, daily, weekly).
- Tag – Apply tags to multiple tests.
- Configure Browsers – Enable or disable selected browsers for chosen tests.
- Copy / Move – Reorganize or duplicate tests between projects or environments.
- Modify Platform – Change the browser platform a test runs on.
- Move to Other Account / Copy to Other Account – Transfer or duplicate tests across accounts and teams.
- Change URL – Replace the base URL for selected tests.
- Rename Test Cases – Bulk update test names.
- Browser Run Order – Switch between parallel and sequential execution.
Copy vs. Move (Within or Across Projects)
- Copy creates a duplicate test in another project or environment. The original remains unchanged. When copying, you can keep test settings, replace URLs, or adjust attributes such as window size.
- When you copy a test case, the system performs a deep copy that includes the execution data from the original test's last successful run.
- This behavior is necessary to establish a performance baseline for the new, copied test instance. By retaining this historical data internally, the new test can accurately measure its own performance and quickly identify deviations or regressions in future executions.
- Please note that while this configuration is vital for technical performance tracking, it currently results in the new test visually appearing as "Executed".
- Move relocates the test. The original is removed from the current project and reassigned to the new one. When moved across environments, Functionize automatically updates the associated URL.
Use Copy when you want to reuse tests in multiple places (e.g., staging vs. production). Use Move when reorganizing or consolidating projects.
Copy vs. Move (Across Accounts)
Bulk Actions also support cross-account operations:
- Copy to Another Account duplicates the test into a new account, preserving the original. You can target a specific team, user, project, folder, and environment in the destination.
- Move to Another Account transfers ownership of the test to a different account. The test is removed from the current account and placed in the selected team, project, and environment.
This enables collaboration across teams without recreating or re-recording tests.
Using Bulk Actions in Projects
- Open the Project to perform the bulk action in.
- In the Test Listing page, click on the checkboxes of the tests to perform a bulk action on.
- Click on the Bulk Action icon to open the dropdown menu.
- Select the action you wish to apply to the selected tests.
Using Bulk Actions in Orchestrations
- Open the Orchestrations page.
- Click on the checkboxes of the orchestrations to perform a bulk action on.
- Click on the Bulk Action button to open the dropdown menu.
- Select the action you wish to apply to the selected orchestrations.
Best Practices
- Use tags before moving or copying tests to make them easier to track later.
- Confirm schedules and environments after a move to ensure the execution context is correct.
- Prefer Copy when in doubt — you can always clean up later, but deleted/moved tests are harder to recover.
- Always preview before applying bulk actions, especially for deleting or updating.
- Confirm dependencies have been addressed before deletions.