Git branching strategy integated with testing/QA process

Question

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. Th

Answer 1

In our company we cant use agile development and need approval for every change by business, this causes a lot of issues.

Our approach for working with GIT is this;

We have implemented "Git Flow" in our company. We using JIRA and only approved JIRA Tickets should be go to production. For Test approval we exted it with a created a seperate Test-Branch.

Steps for processing a JIRA Tickets are:

1. Create a new Branch from Develop-Branch
2. Do the code Changes on the Feature-Branch
3. Pull from Feature the Changes to the Test/QA Branch
4. After business approval we pull the change from feature branch into develop
5. The develop goes frequently in a release and then finally master branch

Splitting each request in an own feature ensures, only approved changes went to production.

The complete process looks like this: