SDLC Studio sprint
A four-agent sprint: Jira, Ticket Steward, Xray, Playwright, then the release check.
What the video shows
- 0:00 The PayStream studio shows Sprint 24 on the Jira board. Run 4-agent sprint starts the run, the Ticket Steward asks which board to use, and Jira is picked at 0:03.
- 0:05 Story PAY-241, a 3-D Secure challenge on high-risk checkout, opens on its Acceptance tab. The Ticket Steward says the criteria are not testable and offers a Gherkin rewrite, which is accepted at 0:07.
- 0:10 PAY-246 and PAY-251 need no fix and move to Ready for QA. The rewrites for PAY-255, PAY-260, and PAY-264 are accepted one after another, and by 0:27 Ready for QA holds 10 cards.
- 0:28 The Test Designer starts, and Xray is picked as the test tool. The cases are written one at a time, each step with an action, data, and an expected result.
- 0:46 The Xray repository lists 15 cases in this run, each tied to a story, and Add to Xray repository saves the set at 0:48.
- 0:50 The Automation Engineer starts with only Playwright checked. The Native runners panel lists each test and prints its steps and a PASS line, from XT-1101 to XT-1703.
- 1:28 The Release Verifier opens Sprint verification, all four checks are ticked, and the increment is signed off at 1:34. The Sprint 24 report shows 4 stories rewritten, 2 that needed no fix, and 15 of 15 scripted runs passed.
The SDLC studio is a free, in-browser sprint with four agents. Ticket Steward rewrites the story on Jira, Azure DevOps, Monday, Trello, Linear, Asana, MS Project, or Backlog. Test Designer writes Gherkin and Xray cases. Automation Engineer generates Playwright, Cypress, and Robot scripts. Release Verifier checks the Definition of Done. No account is needed.
Built by Carlos A. Muñoz, a QA architect with over 18 years in test automation and delivery. Read the interactive CV, open the SDLC studio, or review any public URL.