Store Paths

Before you export paths, you can optimize, filter, name, and store the paths that you most commonly need. You can categorize paths by custom Stored Path Types, such as "Test cases" or "Complexity Cases". After you have stored paths, you view or edit them on the View tab in the Path Explorer.
ard31
Before you export paths, you can optimize, filter, name, and store the paths that you most commonly need. You can categorize paths by custom Stored Path Types, such as "Test cases" or "Complexity Cases". After you have stored paths, you view or edit them on the
View
tab in the
Path Explorer
.

Store Paths

Before you can view paths, select the paths that you want to store.
  1. Open a flow and then open the
    Path Explorer
    .
  2. Use the drop-down menu under
    Stored Path Type
    to categorize your paths.
    Subsequently generated paths are stored under the selected category.
    Default: Test Cases
  3. Click
    Store Path
    ,
    Store Selected
    or
    Store All
    .
    The
    Path Name Template
    dialog opens.
  4. Name the path.
    For information about automatically naming multiple paths, see Use Templates to Name Multiple Stored Paths.
    Do not use apostrophes or double quotes in path names; special characters may cause integration problems.
  5. Click
    OK
    to confirm the path name.
    The paths are stored.

Use Template Functions to Name Multiple Stored Paths

When you store multiple paths of different types, you want to be able to identify stored test cases and tell them apart easily. Use the provided template functions in the Path Template dialog to generate unique path/file names and path descriptions.
  • Path names typically include relevant chosen outputs, unique numbering, or names of relevant blocks in this path.
  • Path descriptions are typically used when exporting paths to initialize a description field in an integrated lifecycle tool. The generated path description is also visible as an uneditable field in the Details View in ARD Studio's Path Explorer.
Use template functions to keep track of mutually exclusive decisions: Insert mutually exclusive Edge template functions together in the same template, for example,
Choose Edge:Red Edge:Yellow Edge:Green
. When generating paths, unused edges generate as empty strings, and only the function for the chosen edge is initialized with text, which results in, for example,
Choose Green
.
Template Set
Optionally, give the
Template Set
a name and click OK. When you name the template set, it is saved with the flow. If you share a flow with colleagues, named template sets are also available to them.
However, a template set does not require a name. If you leave this field empty, the set is saved in your local ARD instance for all flows. It is saved as "(unnamed)" in the Template History. When you share the flow, unnamed sets are not included.
Template Set History
The Template Set History button (clock icon) lets you recall recent and saved template sets, including the five most recent templates from the previous ARD release. If you use a legacy template set, it will be included as a named set in this flow.
  • Click the
    History
    button, select a path type, and select a template set to use in this flow.
    Tip: Hover over a template set name in the History menu to preview the template in the dialog.
  • Click
    History, Recent Template Sets
    to select sets recently used with this flow, as well as legacy sets.
  • Click the X button to delete the current template set from this flow.
Alternatively to using an existing template set, you can create a new template set, as described under Define Path Name Templates.
Path Name Templates
Providing a
Name Template
is required when you store a path. Saved path name templates are available for reuse when you generate path names and path descriptions.
When you use template functions in the file name template, consider that variables can be empty or can have the same values. To ensure unique file names, include the
{Path No}
or
{Next}
template functions to number paths consecutively. If paths are exported with the same file name, ARD appends a number, such as “Path (1)” and so on, to prevent files from being overwritten.
Path Description Templates
The Path Description template is optional, and its three fields (header, body, footer) are empty by default.
The Path Description template consists of a concatenated header, body, and footer. The fields accept multiple lines.
  • The header and footer are the same for all generated paths. The available templates include path and flow functions.
  • The body field only accepts special block-specific template functions. The name generator iterates over all blocks in the path and concatenates the name string by repeating the body template.
The body template has a filter button so you can limit which blocks are considered in the description.
  • Include or exclude process or decision blocks, start or end blocks, or sub-blocks (blocks inside a Subflow Block), or select individual blocks to skip.
  • If a filter is active, the filter button looks pressed.
  • To disable the filter, select all blocks.
Path Description Example
  • Header:
    This is path {Path No} out of {Paths Total}
  • Body:
    Decision {Block No} with name {Block Name} and description {Block Description} selects {Decision Output}
  • Footer:
    This path ended in state {Last Block}
Generates for example the following path description:
This is path 4 out of 12 Decision 1 with name Choose Day and description Date Stamp selects 2020-01-15 Decision 2 with name Preferred Time and description Time Slot selects 10:00-12:00 Decision 3 with name Choose Location and description Office Name selects Head Office This path ended in state No appointment available
Define Path Name Templates
A default name template for each path type is always available.
Choose
one
of the following name template options:
  • Enter a literal path name. Use this option when you are naming only one path.
  • Combine literal text and template functions to name multiple paths. Click a template function in the tree to insert a naming template into the string.
    For a list of all available functions, see Path Naming Template Functions in the reference section.
    Example:
    Test Case {Path No} of {Total No}
  • Create a resolvable expression using the TDoD Service from the CA TDM integration (TDM Data Painter). Choose this option to systematically name test cases based on path data.
    1. Click the
      Edit
      button next to the
      Template
      field.
    2. Log on to the TDoD repository. The
      Select Level
      window opens.
    3. Select a starting level or a saved Flow from the project tree, and click
      OK
      . The
      Data Painter
      window opens.
    4. Define the path name using relevant custom variables, and click
      OK
      .
      Example:
      Test case with claim found = ^ClaimFound^ and inquiry type = ^InquiryType^
      You return to the Path Name Template window.
    5. Enable
      Resolve Path Name Using Path Data
      .
Refresh Path Names and Descriptions
When you add new blocks after you have defined a filter, return to the filter settings and define filtering for the new block manually. For example, if your filter is set to include all decision blocks, and you have added a decision block, you need to include it in the filter manually.
After you have edited a template that is in use, regenerate the names and descriptions of your stored paths:
  1. Open the Path Explorer.
  2. Go to the
    View Test Cases
    tab.
  3. Click
    Recreate Stored Paths' Names and Descriptions
    .

View Paths by Type

There are five default stored path types that you can use to categorize your paths:
  • Test Cases (default)
  • Use Cases
  • Complexity Cases
  • Backup
  • User Stories
To view paths by type, follow these steps:
  1. Click
    Manage, Manage Stored Path Types
    .
  2. Select a
    Stored Path Type
    .
  3. Open the
    Stored Paths
    tab.
  4. Click
    Show in Path Explorer
    to return to the
    View
    tab in
    Path Explorer
    where you can see this path in context.
Use the
Path Collection Editor
to populate a whole path type. For more information, see Populate Custom Path Collections.

Customize Path Types

You can rename or delete existing path types, and add custom path types.
  1. Click
    Manage, Manage Stored Path Types
    , and click
    Details
    .
    To manage path types, you have the following options:
    • Click
      Add path type
      to add a custom path type.
      The
      Details
      tab on the right automatically populates itself with the default details of the new path type.
    • Type the new name into the
      Path Type Name
      field to rename a path type.
    • Click the
      Delete
      icon to delete a path type.
      Note: This also deletes all paths stored under this type.
    • Left-click the
      Path Type Name
      , enter the new name, and click
      Save
      to rename a path type.
  2. Configure the default path types that are used when you create paths.
    1. Go to
      File
      ,
      Configuration
      ,
      General Config
      .
    2. Change the settings on the
      Default Path Types
      tab.

View Cost and Complexity Summary of Stored Paths

Click
Manage, Manage Stored Path Types
. On the
Details
tab, you can view a summary of the following path properties:
  • Stored Paths Count
    The number of paths stored under this type.
  • Current Complexity
    The sum of complexity of all paths stored under this type.
  • Current Cost
    The sum of cost for all paths stored under this type.
  • Default Complexity
    The default level of complexity assigned to each block stored under this path type.
  • Testing Factor
    The proportion of testing costs to implementation costs.
  • Blended Rate Per Unit
    The overall average cost per hour, per employee.

Find and Remove Duplicate Stored Paths

  1. Click
    Manage, Manage Stored Path Types.
  2. Select a
    Stored Path Type
    and open the
    Stored Paths
    tab.
  3. Click
    Remove duplicate paths
    . Or click
    Remove all paths
    to clear all stored paths.

View Details of Stored Paths

  1. Click
    Manage, Manage Stored Path Types.
  2. Select a
    Stored Path Type
    and open the
    Stored Paths
    tab.
  3. Click the
    Details
    icon to view properties of the stored path:
    • General: Name, Notes, Blocks Count, State, Importance, etc.
    • Details: Complexity, Make and Find configuration, etc.
    • Settings: Optimization Type, Decision Table Integration, etc.
    • Modification history
    • Runs
    • People and Roles
    • External Links
    • Automation
    • Custom Fields

Rename Stored Paths

  1. Click
    Manage, Manage Stored Path Types
    .
  2. Select a
    Stored Path Type
    .
  3. Open the
    Stored Paths
    tab.
  4. Left-click a path name, enter the new name, and click
    Save
    .

Analyze the Impact of a Change

If you have stored paths and make changes to the flow, you want to analyze the impact of that change. For larger changes, and to ensure that the optimization produces the smallest set of tests for the highest coverage, we recommend to delete all stored paths and re-run the Optimizer on the updated flow.
For minor changes, the
Path Impact Analyzer
can try to repair affected stored paths by finding a new shortest path.
Follow these steps:
  1. Open the
    Path Explorer
    and go to the
    View Test Cases
    tab.
    The
    Path Impact Analyzer
    opens and shows a list of affected stored paths.
  2. Review the stored paths and read how the latest changes impacted this path.
    Example: A warning "Missing or modified link between nodes." with suggested repair method "Using shortest path between them."
  3. (Optional) Enable the
    Reset the path names to default after repair
    checkbox to refresh the stored paths' names. Disable the checkbox to keep the old names.
  4. (Optional) Press the
    Export
    button to export the affected stored paths as a CSV file.
  5. Choose how to proceed for one or all affected stored paths:
    • Hide All
      Postpones the decision for now, closes the Analyzer window, and returns you to the
      View Test Cases
      tab.
    • Move All
      Moves all affected stored paths into a Path Type, so you can deal with them later.
      Tip: Hide all affected paths to close the window, and create a new Custom Path Type; then return to the
      View Test Cases
      tab to move them all.
    • Delete
      ,
      Delete All
      Removes one or all affected stored paths including their attributes. Use this option if you want to start over because the Analyzer cannot repair the paths. Then use the
      Path Explorer
      to regenerate all paths.
    • Repair
      ,
      Repair all
      Reruns the Optimizer on one or all affected stored paths by finding a new shortest path.