Bitbucket is a web-based version control repository hosting service by Atlassian, for source code and development projects that use either Mercurial or Git revision control systems.
Testim's Bitbucket integration allows you to automatically mirror in Testim the version control functions performed in Bitbucket, so your test versions match the versions managed in Bitbucket. Branches that are created in Bitbucket will be also automatically created in Testim, under the same name. Merging branches in Bitbucket will automatically merge the branches in Testim.
Read more Testim branches here.
This process is required only once.
To enable the Bitbucket integration:
- In Testim, go to Settings > Integration tab.
- Under Bitbucket, click the "login" link.
- Click "Grant Access" button.
Select the repository to connect to. This operation requires admin access to the repositories.
Select the checkboxes with the desired actions:
Create: Whenever a branch is created in Bitbucket, a branch will be also created in Testim.
Merge: Each time Bitbucket branches are merged, Testim will automatically merge your tests.
At this point the Testim project/repository will mirror your Bitbucket repository, so if you want to create a new branch or make a Pull Request and then merge, you should do it in Bitbucket only.
In the following example, we have created a new branch in Bitbucket called demo-bb-integration.
The same branch is automatically created in Testim (which is forked from the Master) and includes all the tests that were in the Master.
If you have created a branch in Bitbucket, in Testim the same branch will always be based on the Master branch. This means that if you want to mirror the branch structure on both sides, make sure the Pull Request is based on the Master branch and not another (non-master) branch.
In the following example, we have made a change in one of the files in Bitbucket and initiated a Pull Request, which will be created in a new branch (pr-branch).
Although in Bitbucket it is possible to merge without a Pull Request, only merges which are part of a Pull Request will be mirrored in Testim.
The same branch is automatically created in Testim.
After the branch is created in Testim, we can also update one of the tests to reflect the changes in the code. At this point we are ready to merge the pull request in Bitbucket.
The same merge will also occur in Testim and tests that were part of
pr-branch (with all the changes) will be merged into the Master branch in Testim.
Updated 18 days ago