How to do test-driven development with merge control and continuous integration
Test Driven Development (TDD) is best practice and the chosen software development process for companies that take their code seriously.
But what about test-driven merge control? Wouldn’t it be nice to make a pull request merge depend on successful test results or even let a successful build in your CI system trigger an automatic merge?
Workzone Auto-Merge with Continuous Integration Systems
Workzone can be set up to automatically merge a pull request triggered by build results. For example, you may have a user-based review and approval process for the pull request from feature and bugfix branches to develop/release branches. The next pull request from develop to master branch doesn’t really need a user-based review. However you want to make sure it built and ran all tests successfully.
- In Bitbucket > Repository Settings > Pull Requests : require 1 successful build
- In Bitbucket > Repository Settings > Workzone : define an auto-merge configuration for develop >> master with ‘Watch Build Result’ turned on
Bamboo
Set up an application link between Bamboo and Bitbucket. Build result notification requests are automatically sent to Bitbucket. Supported Authentication Types: OAuth, Basic Auth
Jenkins
Install the Bitbucket Notifier Plugin and add the Bitbucket base URL and credentials to your plan to send build result notifications. Supported Authentication Types: Basic Auth