DEV Community

Alec Dutcher
Alec Dutcher

Posted on

AZ-400: Implement traceability policies decided by development

End-to-end traceability

  • Supported tasks to facilitate traceability:
    • Create a branch from a requirement
    • Create a pull request of updated branch
    • Validate the pull request using a build pipeline
    • Create and run inline tests on requirements
    • Merge the pull request into the main, default branch
    • Deploy changes into production with deployment status to Azure Boards
    • Monitor and report on requirements traceability
  • Link types used to construct links for Git repositories:
    • Build
    • Found in build
    • Integrated in build
    • Branch
    • Commit
    • Pull request
    • Integrated in release stage
  • Requirements Traceability Matrix
    • Document that links requirements throughout the validation process
    • Ensures that all requirements defined for a system are tested in the test protocols

Image of Datadog

Create and maintain end-to-end frontend tests

Learn best practices on creating frontend tests, testing on-premise apps, integrating tests into your CI/CD pipeline, and using Datadog’s testing tunnel.

Download The Guide

Top comments (0)

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay