Skip to content
Sahi Pro Flowcharts is retired. These pages document the last release (v12) and are no longer updated. Go to the current documentation.Flowcharts is retired. Current docs
Get Free Trial
Sahi Pro Flowcharts is retired. These pages document the last release (v12) and are no longer updated. Go to the current documentation.

Flowchart Paths and Branches

There can be multiple paths/flows in a Flowchart. This allows grouping of similar test flows together.

New Paths can be added in 2 ways:

  1. As a branched subpath to another path
  2. As a new path starting from the Start node.

Many test flows start off with the same steps and then start diverging later. Such flows can be designed using branches.
Branches reduce duplication and give a clear view of the various flows possible from a particular stage in the application.
Sub-Labels can be added to a path at any point to give some context or description to the branched flow.

Branch with Sub-label

  • Any number of branched nodes can be added to a non-Condition Node.
  • A Sub-Label helps in giving more context to a branch. It is not mandatory. It can be added anywhere in a path.
  • Every path can have its own associated Dataset

Controlling Branch Flow with Sub-Label Grouping

Section titled “Controlling Branch Flow with Sub-Label Grouping”

Sub-label groups are used to ensure that paths follow specific branches only.
A sub-label group has two parts - a group name and a value.
It is written in the form <group_name>:<value> inside a Sub-Label node.

In the example below, there is a setup for two types of products - digital and physical, some common actions and then specific verifications for digital and physical. Here we want to ensure 2 things:

  1. For a digital product, shipping address is not needed.
  2. For a physical product, the shipping address is needed.

Adding the sub-label groups ensures that when Product Type sub-label is encountered, the Product Type: Physical will only go through the second Product Type: Physical and not through Product Type: Digital

Branch with Sub-label Group

Some paths are only possible for specific data or only if some specific prior setup has been done.
Conditions can be used to enforce separation of such paths.

Branch with Condition

  • Only 2 branches are allowed from a Condition node

An independent path can be created from the Start node.
Such paths are related in context, but do not need to repeat the steps from another path.

Separate New Path

Call Path is used to invoke one path from another path. It is achieved through adding Call Path node.
This creates a hierarchical structure where paths can reference and invoke other paths, promoting path reusability and modular design.

Eg.

Call Path - Product Coupon

Here Create Coupon calls Create Product as Product should be created before creating Coupon.
Then: When we Automate Create Coupon, we will see the sequence of paths.

Path sequence - Product Coupon

When Create Coupon is run, Create Product will run inside from Create Coupon.
We call paths which run as part of current path as called paths and path which is calling as calling path. In this case, Create Product is a called path and Create Coupon is a calling path.

To view all the branched paths in a table view, click on Table View button on the top of the flowchart.

View All Paths - Table View

Next: Run/Execute Flows