How do we use RM for our test runs

This post details the successful migration of internal VSTS organization testing systems from homegrown tools (RollingTest, tfsruns) to Azure Release Management (RM). It outlines the feature requirements that enabled this transition, including task group reusability, queuing policies, branch/tag filters, deployment status widgets, and task timeouts. The post describes the current usage of RM for setting up CI pipelines for microservices, analyzing failures, and checking release readiness, demonstrating a streamlined workflow for engineers and release owners. It also lists pending 'good to do' features like test deployments in PR workflows and commit-to-deployment status tracking.