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…
Bitbucket Tests vs Jira Test Management: Compare QA Records and Gaps
A green automated test history can help a developer identify a safe-looking change while leaving a QA lead unable to answer a different question:…
QA Capacity Planning in Jira: Match Sprint Scope to Team Availability
A sprint can contain carefully estimated testing work and still overload the only person who can perform it. The missing input may be a…
How to Organize a Jira Test Repository: Folders, Labels, and Ownership
A checkout test appears under Payments, again in a Smoke folder, and once more under the latest release. When the payment rules change, someone…
Jira Requirements Traceability Matrix: Map Stories, Tests, and Defects
A Jira story is Done, a test case is linked, and the related bug is Closed. Can the release owner conclude that the story's…
Localization vs Internationalization Testing: Differences and Examples
A checkout can display translated labels while corrupting a customer's name, hiding the confirmation button, or interpreting the delivery date incorrectly. Reviewing the translation…
Parameterized Test Cases in Jira: Reuse Steps Without Cloning Tests
A quantity-validation rule changes, and the test library contains separate cases for zero items, one item, five items and six items. Each case repeats…
Test Data Management: A Practical Guide to Safe, Repeatable QA Data
A refund test passes in the morning and fails after lunch. The application build has not changed, but another tester has already refunded the…
AI Test Coverage Analysis: Find Requirement Gaps in Existing Tests
A refund story has a linked test called “Refund Permissions.” Its steps check the user's role before the first submission. The current acceptance criteria…
Test Management vs Spreadsheets: Compare History, Reporting, and Cost
A release report shows a test as passed, but the expected result changed after that execution. Can a teammate recover what was tested, on…
Developer-to-QA Handover in Jira: Define Readiness, Context, and Owners
A story moves to Ready for QA, but the tester cannot tell which build contains the change. The acceptance criteria describe yesterday's behavior, and…
Test Run Custom Fields in Jira: Record Failure Reasons With Xray Cloud
A reusable checkout Test can encounter different problems in different executions. One run might show the wrong order confirmation; another might stop at an…
Test Case Approval Workflows in Jira: Roles, Reviews, and Change Control
A refund test case was approved last week. Today, its expected result has changed, but the Jira work item still says Approved. Before the…
Defect Triage in Jira: Set Severity, Priority, Owners, and Next Steps
A Jira backlog can contain several High-priority bugs while leaving the team unable to answer a basic question: what should happen next? One report…
Leaving Zephyr in Jira Cloud: Export Test Cases and Results Before Cancellation
A QA team leaving Zephyr needs more than a spreadsheet that opens successfully. It needs the test definitions it intends to keep, the execution…
Import Test Cases From Excel to Jira: Map Steps and Requirement Links
A spreadsheet can arrive in Jira with every row accounted for and still lose the information a tester needs. Actions may become a block…
Link Existing Jira Bugs to Test Steps: A Zephyr Data Center Guide
A manual test step fails, and the team has already filed the matching Jira bug. The remaining task is to connect that existing issue…
What Is Exploratory Testing? Charters, Session Notes, and Debriefs
A workspace invitation works when a new user follows the expected path. Then the team changes how invitations are revoked. The existing happy-path test…
Bug vs Incident in Jira: Separate Service Recovery From Defect Fixes
A development team can finish a bug fix while customers still cannot use the service. A response team can restore service while the underlying…
AI Test Case Generation: A Requirements-to-Review Workflow for QA
A generated case says, “Enter an invalid quantity and verify the correct error.” It has a title, steps, and an expected-result field, yet another…
Risk-Based Testing: How to Score Risks and Prioritize Your Tests
A release changes payment retries, tax calculations, and stock updates. One tester has four hours before the release review. Running the shortest tests first…
Smoke vs Sanity Testing: Key Differences and When to Use Each
A new checkout build reaches the test environment. Before assigning detailed tests, you need to know whether users can sign in, find a product,…
Jira Test Execution Explained: Assignments, Statuses, and Blockers
A Jira item marked Done does not, by itself, tell a QA lead whether the checkout tests passed. The testing work may have finished…
7 Test Environment Management Checks to Run Before Test Execution
A regression run fails halfway through checkout. The team can investigate the application, but first it needs to know whether the same build is…