Resources for Test Management in Jira
Practical guidance on Jira test management, test cases, release testing, AI-assisted QA, and Sherlock. product updates.
Flaky Test Quarantine: Owners, Expiry, and Nonblocking CI Results
A confirmed flaky test can block unrelated changes without providing a dependable release signal. Removing that obstruction is reasonable only if someone still sees…
Trigger GitLab Tests From Jira Cloud: Set Up On-Demand QA Runs
A tester reviewing a Jira issue may need a fresh smoke run without opening GitLab and choosing pipeline parameters. A manually triggered Jira Cloud…
Jira API Rate Limits for QA Integrations: Handle 429s With Safe Retries
A regression-results worker receives HTTP 429 while reading Jira issues. Sleeping that worker may be necessary, but it will not help if other workers…
AI Test Failure Analysis: Trace Logs to a Root-Cause Hypothesis
A checkout test times out while waiting for an order confirmation. The runner reports an assertion failure, the application records a failed request, and…
AI Exploratory Testing vs Scripted Tests: Roles, Evidence, and Limits
A recipient-preview rule changes, but the regression suite still checks the earlier behavior. An AI agent may choose a different route through the editor…
Integration Testing vs End-to-End Testing: Differences and When to Use Each
A registration endpoint returns success and saves an account, yet the person signing up never reaches an authenticated session. The verification message might contain…
AI Testing Agents: How to Evaluate Reliability, Cost, and CI Readiness
An agent completes checkout, reports success, and attaches a screenshot. That looks useful until you discover that it avoided the discount path you needed…
Load Testing vs Stress Testing: Goals, Metrics, and When to Use Each
A checkout service can meet its response-time targets during a forecast sales peak and still remain unhealthy after an unexpected surge. Requests may accumulate…
Manual vs Automated Testing: Differences, Costs, and Best-Fit Uses
A checkout change can leave a team with two different jobs: confirm that agreed discount rules still produce the right totals, and investigate whether…
Self-Healing Test Automation: How AI Agents Repair Tests Safely
A checkout test fails after a UI update. An AI agent changes its locator, reruns the test, and returns a passing result. Before accepting…
Jira Incoming Webhooks for QA: Authenticate and Verify CI Callbacks
A CI job can receive HTTP 200 from Jira Cloud while the intended automation rule never runs. Atlassian documents this behavior for the post-May…
Statement Coverage vs Branch Coverage: Differences With Worked Examples
A test can execute every statement in a function while leaving a decision's false exit untouched. A green statement-coverage result can therefore hide a…
Test Pyramid Explained: Place Unit, Integration, and E2E Tests by Behavior
A checkout test reports that the confirmation page never appeared. The failure could come from quantity validation, a payment response, a database write, or…
Test Automation Strategy: Scope, CI Feedback, and Ownership Decisions
A checkout change is ready for review, but its browser suite is still running. The first failure disappears on retry. Nobody knows whether the…
Playwright Jira Integration: Send Test Results Through Xray and CI
A Playwright job can produce a valid JUnit XML file while Jira shows no new test results. The report may never have been uploaded,…
Flaky Test Detection: Use CI History Without Hiding Real Regressions
A checkout test fails because the confirmation page never appears. Its retry passes, and CI finishes green. The team still needs to know whether…
Jira QA Automation: Prevent Duplicate Tasks and Rule Loops in Cloud
A story enters Ready for QA and Jira creates a testing subtask. After rework, the story enters the same status again and receives another…
How to Sandbox AI Testing Agents With Scoped Accounts and Network Rules
A browser agent asked to test checkout may inherit more authority than the test needs: an administrator session, access to other tenants, or a…
Consumer-Driven Contract Testing: Verify API Compatibility in CI
A consumer changes the response field it needs. The provider passes its build, yet the consumer still breaks after deployment because production runs a…
How to Write Gherkin Scenarios With Clear Given-When-Then Examples
A checkout test says “delivery works,” but two reviewers disagree about whether a discount should remove free shipping. Adding more clicks to the test…
AI Visual Testing: Set Match Rules and Review Baselines Before Approval
A checkout screenshot stops failing after the team relaxes its comparison rules. That could mean a changing date no longer creates unnecessary alerts. It…
Service Virtualization: Test Unavailable Dependencies Without Waiting
Your checkout change is ready to test, but the stock-reservation provider's sandbox is unavailable. Waiting blocks feedback on your own code. Replacing every dependency…
AI Test Script Generation: Convert Manual Cases Into Playwright Tests
An AI-generated test can click the correct button and still verify the wrong result. A script that reaches an order confirmation has not necessarily…
Test Automation ROI: Calculate Payback With Build and Maintenance Costs
A regression suite can run faster without reducing the payroll bill. It can also execute more often while nobody stops performing the original manual…