Epsilon3 is a powerful suite of tools for fast moving engineering teams to manage many facets their plan, build, test, and analysis work.

A core aspect of the tool suite is the ability to write and execute test procedures. These test procedures frequently form a part of the verification evidence that needs to be linked to the relevant requirements in Flow to give full traceability. Flow's integration with Epsilon3 is designed to achieve exactly this.

Integration Setup

In order to link Epsilon3 to Flow you will first need to generate an Epsilon3 API key. You can do this from Epsilon3's settings.

Once you have this, it needs to be entered in Flow's settings under Integrations -Epsilon3.

Linking an Epsilon3 Procedure to a Requirement in Flow

The integration takes a master procedure from Epsilon3, it looks at runs of that procedure that have already ended, and it takes the status of the latest run. That status is fed into any linked requirements in Flow as the verification status of the requirement.

To link a procedure to a requirement, first go to the list of master procedures in Epsilon3 and copy the URL of a released version of the relevant procedure.

Within Flow this URL must be pasted into a new Document. If the Epsilon3 logo shows up next to the URL the procedure has been read correctly.

When this document is linked to a requirement (in the verification tab of the details pane), the status of the latest run of that procedure will be reflected in the requirement.

To show this status at the top level of the requirement in table view and tree view, make sure the requirement has a check added that is set to Document.

Keeping Track of Changes

As new runs of the procedure occur in Epsilon3, Flow will pull data and reflect the status of the latest run. New data is pulled each time the requirement is opened, closed or refreshed in any other way.

Walkthrough Video