How is the Git Branching strategy used in development?
Our development team has been using the GitFlow branching strategy and it has been great ! Recently we recruited a couple testers to improve our software quality. The idea is that every feature should be tested/QA by a tester. In the past, developers work on features on separate feature branches and merge them back to the develop branch when done.
When to use Git Branching for QA automation?
A new release, let’s say Release-5, is in development and there are few sprints planned for it. The test team is supposed to deliver automated tests for every feature build in the Sprints. There can be multiple features in the Sprint as well, depends on its size. For this discussion, assuming there are.
How is a feature tested in a git branch?
The idea is that every feature should be tested/QA by a tester. In the past, developers work on features on separate feature branches and merge them back to the develop branch when done. The developer will test his work himself on that feature branch. Now with testers, we start asking this Question
When does a tester merge a branch in Git?
When the developer is done with deployment and the feature is ready to be tested he merges the develop branch on the feature branch and deploys the feature branch that contains all the latest develop changes on TEST. The tester tests on TEST. When he is done he “accepts” the story and merges the feature branch on develop.
What should the naming convention be for a Git deployment branch?
Create a clear naming convention, such as deploy/performance-test, and treat the environment branches like release branches. Your team should agree on a process to update deployment branches with the code from your main branch. Cherry-pick bug fixes in the deployment branch back to the main branch.
Are there any release branches in Git flow?
We are trying to adopt the successful Git branching model implemented by git-flow. Now, we are working on at least two release-branches, one for the latest stable release and one for the next (“preview”) release. What I don’t understand is why all releases seems to “linearized” to the master and tagged there.