How can QA test multiple features at once with feature branching in Gitflow workflow?

If developers were to work on different branches for different features I understand that they can give a QA build from the feature branch and once it is tested it can be merged with “develop”. But if the QA team is fairly large and can test multiple features at once how can they be given a build containing features that are residing in different branches?

  • GIT: What happens during branching?
  • git - what is the best practice for team work on a feature branch?
  • Working with old releases in Git Workflow
  • Move branch to another branch
  • Can any source control system handle branching code base on a per client basis?
  • Reverting an invalid git merge
  • How can you unstash changes using EGit?
  • How do I reword a commit (message) that is the parent of two branches?
  • Best pratice for multiple custom projects and Git
  • .gitmodules changes with multiple git users, causing a constant headache
  • Eclipse code not indent properly in git
  • Splitting large git repository
  • One Solution collect form web for “How can QA test multiple features at once with feature branching in Gitflow workflow?”

    But if the QA team is fairly large and can test multiple features at once how can they be given a build containing features that are residing in different branches?

    That would be by:

    • setting up an integration branch, reset to the latest master,
    • asking for the developers to push their feature branch OR
    • or fetching the different developer’s repositories, and merging the right feature branches in the integration branch
    • running tests in said integration branch
    Git Baby is a git and github fan, let's start git clone.