Integration With Lifecycle Tools

provides a consistent integration with several lifecycle tools.
ard28
Agile Requirements Designer
provides a consistent integration with several lifecycle tools.
The lifecycle tool integration offers the following capabilities:
2
Connect to a Lifecycle Tool
Each lifecycle tool in
Agile Requirements Designer
has its own connector option.
  1. Go to
    Toolbox, Connectors
    ,
    tool name.
  2. Enter the instance URL and your username and password.
    You can now browse content and run queries.
    Note:
    The integration only displays projects that you have configured.
You can customize default view settings and default behaviors for each lifecycle tool. Go to
File
,
Configuration
,
tool name
to open the configuration dialog.
Configure Lifecycle Tool Projects
Configure the lifecycle integration before exporting or importing. Otherwise, the following error message appears:
It appears you have no correctly configured projects. Only correctly configured projects will be made visible.
Click
Set up Configuration
in the error message to directly open the "
General Configuration
" Dialog to configure your entities.
To learn more about configuring projects, see Configure Lifecycle Tool Integration.
Import From a Lifecycle Tool to
Agile Requirements Designer
After you have configured the project, you use the Rich Text Importer to import test cases from lifecycle tools. Before you import test cases, format the descriptions in the lifecycle tool so that the rich text importer can parse them easily into blocks. The best practice is to have each test case step on a separate line. Each line then becomes a block in the
Agile Requirements Designer
flow. You can fine-tune the formatting of the imported text directly in the Rich Text Importer dialog while importing. For more information, see Import Rich Text.
It is possible to map a work item to more than one level in
Agile Requirements Designer
. For example, a TFS User Story can be mapped to Block and Flow. These work items are ambiguous and need to handled during import.
Follow these steps:
  1. Create a flow in
    Agile Requirements Designer
    .
  2. Go to
    Toolbox, Connectors
    ,
    tool name
    , and enter the instance URL and your username and password.
  3. Drag an object from the tree in the Connectors dock, and drop it on to the canvas. Dragging multiple selected objects is not supported.
    • (If the entity is not mapped)
      Agile Requirements Designer
      prompts you to configure the mappings before you can continue. For more information, see Configure Lifecycle Tool Integration.
    • (If you import an ambiguous work item)
      Agile Requirements Designer
      prompts you to specify the import type. Click one of the import types:
      Block
      ,
      Path
      , or
      Flow.
    The Rich Text Importer opens.
  4. Review how the Rich Text Importer parsed the description of the Parsed Blocks.
    If you are not happy with the result, reformat the imported text, or manually adjust blocks using the
    Merge Selected
    button.
  5. Click
    OK
    .
  6. If prompted, click
    Yes
    if you want to attach start and end blocks.
  7. If prompted, click
    Update
    to re-layout the imported flow to make it better readable.
    The work items are imported.
    (For TFS, CA Agile Central (except folders), and JIRA only)
    Agile Requirements Designer
    creates an application link for imported Paths on the Path level. For imported Blocks, it creates an application link under the Block properties.
  8. (Optionally) Repeat and import more paths.
  9. Connect the imported blocks manually where needed, and define outputs to create a working flow.
Export From
Agile Requirements Designer
to a Lifecycle Tool
After you have configured the project, you can use export items from
Agile Requirements Designer
to a target place on the lifecycle tool's server side. The type of exported object depends on the target tool. The object types are Block, Path, and Flow.
Export is not supported for Blueprint StoryTeller.
Choose one of the following export options:
  • If the integration you are using can export paths, choose the Export Path option from "Path Explorer".
    1. Define and save your paths.
    2. In the Toolbox Dock, click
      Connectors
      and select the lifecycle tool.
    3. In the Connectors Dock, provide your credentials to log in to the tool server.
    4. In the
      Path Explorer
      , go to the
      View
      tab and click the
      Export Paths
      icon. Select your lifecycle tool from the drop-down list.
    5. Select the target project and location to which you want to export the user stories and click
      OK
      .
    6. Select the user stories that you want to export and the target
      Entity Type
      . For example, "Issue: Test Case".
    7. In the dialog that appears, name the new user story, and click
      OK
      .
      Agile Requirements Designer
      validates your input.
    8. The user story is exported from
      Agile Requirements Designer
      and imported to the lifecycle tool.
  • If the integration you are using can export "Paths" or "Blocks", you can also choose the export buttons from the Connector panel.
    1. Open the Connector panel and log in to the lifecycle tool.
    2. Click the first button to export a Flow, and the second button to export a Block.
      Tip: Hover over a button to see a tooltip.
      image2017-2-22 15:53:22.png
Not all integrations offer all export options. The drop-down options to select an
Entity Type
only show correctly configured entity types for the
Agile Requirements Designer
object type that you are exporting. For example, if you export the object type "Paths" from within
Path Explorer
, you only see entity types that you have previously correctly mapped as Paths.
Define Optional Export Options
You have several extra options in the dialog when exporting.
Block
  • Attached Images – Constructs and attaches images which are attached to the block itself.
Path
  • Path Image – Constructs and attaches the image of the test case in the flow.
  • Expand SubFlow – If the Stored Path has subflows, it uses every block from the subflows.
  • Include SubFlow – If a stored path has subflows, it does not use blocks from the subflow. The test case represents each subflow as a single step.
  • Test Data – Constructs and attaches a CSV file of test data for this path. This export includes default test data variables. These variables are defined in the flow (and its subflows) properties but do not occur in the path being exported. The file name is truncated to 70 characters and has a
    _TestData.csv
    suffix.
    Tip: To find the variables in flow properties, click
    Manage, Properties, Variables
    .
    • Exclude Default Test Data Variables – Excludes default test data variables for the path being exported.
  • Attach Automation – Constructs and attaches an automation script for a given layer.
Flow
  • Flow Image – Constructs and attaches an image of the flow.
Define Default Export Options
For each possible export option (except attaching automation scripts), you can define defaults.
  1. Open
    Configuration, Connectors Options
    .
  2. Enable defaults available for the respective lifecycle tool.
    Example: If you always want to attach an image when exporting to JIRA, enable "Default Export Image".
    • Default Export Include SubFlow
    • Default Export Expand SubFlow
    • Default Export Image
    • Default Export Attached Images
    • Default Export Test Data
    • Default Export Test Scripts
    • Default Block Export Type
    • Default Path Export Type
    • Default Flow Export Type
  3. Click Save.