Feature Requests & Ideas

For bug reports and questions, please use the in-app chat or support@mabl.com.

Branching: conflict resolutions, pull latest changes

Currently the branch that has latest changes overwrite the master when merged, and there is no way to select how the changes should be merged.

There is also no possibility to pull latest changes to current branch from master or from another branch that prevents proper integration of Mabl tests in Agile process.

  • Iryna Suprun
  • May 13 2021
  • For Consideration
  • Attach files
  • Guest Guest commented
    13 Jan 04:14pm

    I have two main issues with branching currently:

    If there are multiple tests on a branch, merging a single test from a branch into master. A workaround for this was to add the respective test onto a third empty branch, and then merge that third branch into master.

    It would also be great to be able to grab flows (or certain steps) that have been created on a second branch for use within the master branch, without having to merge the whole of the second branch, or having to re-train those steps on the master version.

  • Madhusmita Mahapatro commented
    9 Jun, 2021 12:02pm

    Good to have a working branch in MABL before merging to Master

  • Guest commented
    9 Jun, 2021 11:42am

    Just my thought.

  • Guest commented
    9 Jun, 2021 11:40am

    It would be great to see flows have been updated before merging.

  • Guest commented
    25 May, 2021 02:06pm

    This would be great. Another feature related to this is to see an actual diff between what is being merged. It would be great to see if any flows have been updated before merging.

  • Guest commented
    14 May, 2021 04:27pm

    This came up with Xandr recently as well and will certainly be something we need to implement to bring parity with what engineers think of when they think that a tool supports branching.

Copyright © 2021 mabl Inc. All rights reserved.