Testing & protection

Verified Delivery Report

Know what was actually checked.

See what was checked for a specific task and the evidence recorded.

01
The report separates recorded results from criteria that have not been tested.Actual Linqbase interface · demonstration project
TURN IDEAS INTO POSSIBILITIES

Know what was actually checked.

After delivery or before accepting the result.

“Finished” can hide untested requirements. A delivery report links the task, recorded evidence and file version so you can judge the result.

Inspect acceptance criteria, commands, tests and limitations. Recheck the version if files changed after the report was created.

YOUR NEXT STEP

How to get started.

From your first choice to the result. Here is how to use this feature in your own project.

  1. 01

    Select a task with stored delivery information.

  2. 02

    Review acceptance criteria, executed commands, outcomes and linked evidence.

  3. 03

    Open details or export the report to assess that version later.

IN PRACTICE

How it could work for you.

Review a navigation requirement and see whether there is matching test evidence or whether it remains untested.

How to assess the result

Only available evidence is reported. Missing tests do not become green merely because the task ended.

GET STARTED IN LINQBASE

Where to find it.

Dashboard → Verified Delivery Report → Show more; or Tools → Verified Delivery Report

Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.
SAVE & CONTINUE

What is saved?

The report remains linked to the task and relevant project state.

GOOD TO KNOW

What you need to know

Not tested does not mean passed. The report is not certification of the whole application and does not automatically update after later code changes.