For the complete documentation index, see llms.txt. This page is also available as Markdown.

Verifications

Violet supports use of Verification entities, as well as direct linking of requirements to associated Violet entities (tests, analyses, etc.).

Using Violet Verifications

Violet Verifications are separate entities from requirements, which can be linked to one or many Violet Requirements and have their own attributes and status. Show or hide verifications using the column selector.

Custom Violet Verifications Attributes

Add custom attributes to Verifications in Custom fields. By default, each Verification has Name, Assignees, Status, and Evidence attributes.

Creating Verifications

From the requirements table view with Verification columns shown, double click in a requirement's row under the Verification heading to create a new verification against the requirement. Enter data in the side panel and click OK. Use the Requirements drop down to select one or more requirements that will be addressed by this Verification.

Adding Evidence

Each Verification can have an Evidence item added, with its own description, status, URL or link to another Violet entity. Add one or many attachments as necessary to support requirement closure.

Linking Requirements Directly to Other Verifying Entities

If you'd rather directly link a Violet Requirement directly to the test run, ticket, or other entity representing the verification work, follow the approach below.

Attach a Verification

Attach a Verification to a Violet Requirement via the Verified by relationship.

In the Requirement edit pane, use the keyword search to find and attach the appropriate verification entity (test, analysis, etc.):

Verifiers

Once linked, users assigned to the Verification will auto-populate the Verifiers field.

Automatic Verification Status Tracking

As the verification is updated (eg. from draft, to in progress, to done), the Verification Status field will auto-update.

Last updated

Was this helpful?