Master Read Only State

Don't allow writing directly to master (only by using branches and merges)

Testim features the ability to lock the master branch, so that writing directly to master is not allowed.
In order to write to the master, all users will need to first fork to another branch and then perform a merge to the Master branch. The merge to master can be done through a Pull Request.


Only the project owner or the company owner can configure the master to be read-only.


This is a PRO feature

This feature is only open to projects on our professional plan. To learn more about our professional plan, see here.

Enabling the master read-only mode

The master read-only mode is located under the Pull Requests settings, in the Settings -> General screen and is configured per project. To enable it, switch on the Protect master from changes toggle. The master will be labeled as "read-only".


Master as read-only behavior

When enabling the master to be read-only, the current activities will be affected.

Testim Editor

  • When performing a save to a test directly under the master, we will ask you to perform a fork to another branch, and save the changes on the new branch

Test List


The following actions will be disabled:

  • Create a new test
  • Delete test
  • Clone test
  • Create a new folder
  • Move to another folder
  • Delete folder
  • Change test's status
  • Rename


The following actions will be disabled:

  • Create suite
  • Copy suite
  • Delete suite
  • Edit suite

Auto-Improve feature will not apply

By default, the auto-improve feature only runs on master branches that are not set as read-only. You can modify the settings to allow the auto-improve feature to run on master read-only branches. For more information see Allowing Auto Improve on a Master Read Only Branch.