Verification Status needs for Requirements Management work item transition

Verification Status - The current test state of a requirement. Can have three values: satisfied, failed, unverified.

Requirements

Verification Status Badge Display

  • When a requirement is created, it's verification status is set to the default value of unverified.
  • The verification status badge will be displayed for each requirement if the requirements verification status is not unverified.

Manual Verification

  • When a requirement is edited, the satisfied check box will display checked if the requirement's verification status is set to satisfied.
  • When a requirement is edited, the satisfied check box will display unchecked if the requirement's verification status is set to failed or unverified.
  • When a requirement is edited and the satisfied check box is transitioned from unchecked to checked, the requirement's verification status will be set to satisfied.
  • When a requirement is edited and the satisfied check box is transitioned from checked to unchecked, the requirement's verification status will be set to failed.

Requirements Report CI/CD Job

  • When the pipeline stage variable allow_failure is false, and the requirements report job is completed without failure, the requirements report will update all referenced requirements to the appropriate verification status.
  • When the pipeline stage variable allow_failure is true, and the requirements report job is completed, the requirements report will update all referenced requirements to the appropriate verification status.

Logging

  • Whenever the verification status of a requirement changes, the change should be logged.
  • When the verification status is modified by toggling the satisfied check box, a timestamp and username will be logged, as well as the state change.
  • When the verification status is modified by the requirements report pipeline job, a timestamp and job identifier will be logged, as well as the state change.
  • When the verification status is set to the current value (unmodified) by the requirements report pipeline job, a timestamp and job identifier will be logged, as well as the current state.

Filtering Requirements

  • The user should be able to filter requirements based on verification status.

Agreed Scope (draft)

  • The existing requirements list will remain.
  • Clicking on a requirement in this list will open the requirement in full-page, work item view.
  • This view will render the Requirement using the Work Items API.
  • The API will provide a title and description using existing work item widgets.
  • A new 'Verification status' widget will provide data from the latest test report.
  • The new view will render the verification status using this Widget.
  • Clicking "New requirement" from the list will open in a full page view, reusing the existing "New Work Item" view.
  • Completing this form and submitting it will create a Requirement Work Item
Edited by John Hope