Feature Requests & Ideas
For bug reports and questions, please use the in-app chat or support@mabl.com.
For bug reports and questions, please use the in-app chat or support@mabl.com.
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
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.
Good to have a working branch in MABL before merging to Master
Just my thought.
It would be great to see flows have been updated before merging.
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.
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.