I’m handling all testing activities in Jira and keep updating my test suite as our software grows through each development cycle.
Our team follows 2-week iterations, and typically I need to validate about 10 development stories each iteration. Currently, I either reuse relevant test scenarios from my existing suite or build fresh ones when required.
My challenge is that I lack proper monitoring and visibility into test execution results (pass, fail, or blocked status).
What I’m wondering:
Would it make sense to set up a Test Run in JIRA for every development story?
How should I structure this to properly monitor testing activities within each iteration and get clear reporting?
Right now I don’t have any reporting system. Since I’m the sole QA engineer on this project, I typically execute tests manually without following any structured execution process where I document results as pass or fail.
Had the same issue as the only QA on a project. Skip creating separate Test Runs for each dev story - it’s a pain. I switched to one Test Run per sprint that covers all test cases across multiple stories. Way easier to track everything without managing tons of runs. For reporting, I just used Jira’s built-in test execution fields with a simple dashboard. Gave me clean pass/fail rates and let me handle blocked tests without drowning in paperwork. Start with one test run per sprint and tweak it as your team grows.
Create a simple test execution issue type and link it to your stories. Don’t get bogged down with fancy test runs - I’ve seen teams waste time on over-complicated processes. Add basic fields for test status and notes, then filter by sprint for your pass/fail metrics. Lightweight approach that gives you proper tracking without the overhead.
I’ve been tracking tests in Jira for three years. Skip Test Runs for now - start with organizing your test cases properly first. Link test cases directly to user stories using Jira’s native linking. For execution tracking, just add a custom status field to your test cases for sprint work. This scales way better than juggling multiple test runs and gives you the visibility without extra hassle. Get your test case structure locked down first, then worry about Test Runs later if you actually need them.