<!-- Google Tag Manager (noscript) -->
	<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-P44THP6"
	height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->{"id":5761,"date":"2026-11-12T16:50:24","date_gmt":"2026-11-12T11:20:24","guid":{"rendered":"https:\/\/bugasura.io\/blog\/?p=5761"},"modified":"2026-11-12T16:50:24","modified_gmt":"2026-11-12T11:20:24","slug":"what-should-qa-test-when-code-changes-beyond-the-ticket","status":"publish","type":"post","link":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/","title":{"rendered":"The Ticket Says One Thing. The Code Changed Five Things. What Should QA Test?"},"content":{"rendered":"<span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\"><\/span> <span class=\"rt-time\"> 8<\/span> <span class=\"rt-label rt-postfix\">minute read<\/span><\/span><p><b><span data-contrast=\"auto\"><img data-recalc-dims=\"1\" decoding=\"async\" class=\"alignnone wp-image-5762 size-full lazyload\" data-src=\"https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?resize=1080%2C441&#038;ssl=1\" alt=\"\" width=\"1080\" height=\"441\" data-srcset=\"https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?w=1080&amp;ssl=1 1080w, https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?resize=300%2C123&amp;ssl=1 300w, https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?resize=1024%2C419&amp;ssl=1 1024w, https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?resize=768%2C314&amp;ssl=1 768w, https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?resize=1536%2C628&amp;ssl=1 1536w, https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?resize=400%2C164&amp;ssl=1 400w\" data-sizes=\"(max-width: 1080px) 100vw, 1080px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 1080px; --smush-placeholder-aspect-ratio: 1080\/441;\" \/><\/span><\/b><\/p>\r\n<p><b><span data-contrast=\"auto\">Quick answer:<\/span><\/b><span data-contrast=\"auto\"> When a code change affects more than the ticket describes, QA should test the requested behavior, every affected dependency, critical user journeys, and any high-risk regression areas. Start with the actual code changes and their dependencies, then prioritize tests by failure impact not just by the ticket\u2019s acceptance criteria. Document the expanded scope and the risks you cannot cover.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">A ticket says, \u201cUpdate the checkout validation message.\u201d The pull request also changes a shared validation function, modifies an API response, and touches a component used by the account settings page.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">The ticket is small. The potential blast radius is not.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">This is a common release-testing problem: QA receives a description of the intended change, but the implementation affects more than the ticket reveals. Testing only the acceptance criteria can miss regressions. Testing the entire application for every change is rarely practical.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">The real question is <\/span><b><span data-contrast=\"auto\">what should QA test when the code changes beyond the ticket?<\/span><\/b><span data-contrast=\"auto\"> The answer requires a repeatable way to connect code changes to affected behavior, assess risk, and select the right regression tests.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">Why Ticket Scope and Test Scope Are Not the Same<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><span data-contrast=\"auto\">Ticket scope describes the behavior a team intends to change. Test scope describes the behavior QA must verify to establish that the change works and has not damaged related functionality.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">These scopes should overlap, but they should not be identical.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">A ticket might describe one user-visible change while the implementation touches shared services, database queries, permissions, or API contracts. Conversely, a large pull request may contain many files but affect only a narrow behavior. File count alone does not tell QA how much testing is necessary.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">Consider a change to a shared date-formatting utility. The ticket may concern invoice dates, but the same utility might render subscription renewal dates, activity timestamps, and report filters.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">QA should not automatically test every screen that imports the utility. It should identify which behaviors depend on the changed logic, how those behaviors could fail, and which failures would matter most.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">What Should QA Test When Code Changes Beyond the Ticket?<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><span data-contrast=\"auto\">QA should expand testing in four directions: the intended behavior, directly affected components, dependent workflows, and high-impact regression risks. The exact scope depends on the change, its dependencies, and the consequences of failure.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">Use this checklist before deciding that a ticket is ready to release.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ol>\r\n<li aria-level=\"3\"><b><span data-contrast=\"none\"> Verify the requested behavior<\/span><\/b><\/li>\r\n<\/ol>\r\n<p><span data-contrast=\"auto\">Start with the ticket\u2019s acceptance criteria. Confirm that the original requirement works under normal conditions, expected edge cases, and relevant invalid inputs.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">For the checkout validation example, test a valid address, a missing required field, an invalid postal code, and the expected error message. This establishes whether the requested change itself works.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ol start=\"2\">\r\n<li aria-level=\"3\"><b><span data-contrast=\"none\"> Identify what the code actually changed<\/span><\/b><\/li>\r\n<\/ol>\r\n<p><a href=\"https:\/\/docs.github.com\/en\/pull-requests\/how-tos\/review-pull-requests\/reviewing-proposed-changes-in-a-pull-request\"><span data-contrast=\"none\">Review the pull request<\/span><\/a><span data-contrast=\"auto\">, changed functions, shared components, configuration changes, API contracts, and database interactions. Ask the developer which behavior or dependency motivated each change outside the ticket\u2019s apparent scope.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">If the team cannot explain why a shared function changed, treat that as a visibility gap not as proof that the change is unsafe. Clarify the reason before finalizing the test plan.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ol start=\"3\">\r\n<li aria-level=\"3\"><b><span data-contrast=\"none\"> Trace dependent behavior<\/span><\/b><\/li>\r\n<\/ol>\r\n<p><span data-contrast=\"auto\">Find the other workflows that rely on the changed component or contract. A shared validation function might serve checkout, profile updates, and saved payment methods.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">Test the dependent workflows most likely to be affected. Prioritize those that use the changed logic in a different way, rather than repeating the same happy-path test across similar screens.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ol start=\"4\">\r\n<li aria-level=\"3\"><b><span data-contrast=\"none\"> Cover failure modes and critical journeys<\/span><\/b><\/li>\r\n<\/ol>\r\n<p><span data-contrast=\"auto\">Check boundary values, error handling, permissions, data integrity, and recovery behavior when relevant. Then verify critical end-to-end journeys that cross the changed component.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">For checkout, that could mean confirming that a valid order still completes and that invalid input does not create an order with incomplete data.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ol start=\"5\">\r\n<li aria-level=\"3\"><b><span data-contrast=\"none\"> Make remaining risk visible<\/span><\/b><\/li>\r\n<\/ol>\r\n<p><span data-contrast=\"auto\">Record what was tested, what was not tested, and why. If a high-risk dependency could not be verified before release, communicate that limitation to the release owner rather than silently treating the ticket as fully covered.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">Code Change Impact Analysis: Find the Blast Radius<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><a href=\"https:\/\/bugasura.io\/requirements-management\"><span data-contrast=\"none\">Code change impact analysis<\/span><\/a><span data-contrast=\"auto\"> connects a code modification to the application behavior it could affect. It helps QA avoid both extremes: testing only the ticket and rerunning every test after every change.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">A practical impact analysis combines technical evidence with product knowledge.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<table data-tablestyle=\"MsoNormalTable\" data-tablelook=\"1696\" aria-rowcount=\"7\" aria-colcount=\"3\">\r\n<tbody>\r\n<tr aria-rowindex=\"1\">\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Evidence<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">What QA should investigate<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Testing implication<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"2\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Changed function or shared component<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Which workflows call it?<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Add regression tests for affected workflows<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"3\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">API request or response changes<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Which clients and integrations consume it?<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Test contract compatibility and dependent journeys<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"4\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Database or schema changes<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Could existing data, migrations, or queries break?<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Test persistence, migration safety, and older records<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"5\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Authentication or permission logic<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Which roles and access paths depend on it?<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Test allowed and denied access<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"6\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Configuration or environment changes<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Which environments or feature flags behave differently?<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Validate relevant environment-specific paths<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"7\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">UI-only change<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Does it affect navigation, validation, accessibility, or responsive layouts?<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Test affected screens and user interactions<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<p><span data-contrast=\"auto\">Use source control diffs, dependency graphs, test history, service ownership, and developer input where available. No single signal is sufficient: a tiny change to shared authorization logic can carry more risk than a large isolated UI change.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">Also distinguish between a <\/span><b><span data-contrast=\"auto\">possible impact<\/span><\/b><span data-contrast=\"auto\"> and a <\/span><b><span data-contrast=\"auto\">confirmed impact<\/span><\/b><span data-contrast=\"auto\">. A dependency may be connected to the changed code without being behaviorally affected. Use targeted tests to establish which risks are real.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">Risk-Based Testing: Prioritize What Matters Most<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><a href=\"https:\/\/bugasura.io\/blog\/test-management-strategy\/\"><span data-contrast=\"none\">Risk-based testing<\/span><\/a><span data-contrast=\"auto\"> helps QA choose tests based on the likelihood of failure and the consequences if something breaks. It is especially useful when the changed code has a wider impact than the ticket suggests and the team cannot rerun every test.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">A simple prioritization model is:<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><b><span data-contrast=\"auto\">Risk priority = likelihood of failure \u00d7 impact of failure<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">This is a decision aid, not a precise probability calculation. Teams can score each factor as low, medium, or high, then use the result to decide what needs the strongest coverage.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">For example:<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<table data-tablestyle=\"MsoNormalTable\" data-tablelook=\"1696\" aria-rowcount=\"5\" aria-colcount=\"4\">\r\n<tbody>\r\n<tr aria-rowindex=\"1\">\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Change<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Likelihood<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Impact<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Suggested priority<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"2\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Copy change on an isolated help page<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Low<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Low<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Basic verification<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"3\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Shared validation logic used by three workflows<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Medium<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">High<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Targeted regression across all three<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"4\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Permission check used by administrative APIs<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Medium<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Very high<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Focused negative tests and critical-path regression<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"5\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Database migration affecting existing records<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Medium<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Very high<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Migration, data integrity, rollback or recovery checks<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<p><span data-contrast=\"auto\">Adjust the priority when evidence changes. A historically flaky test may need investigation, but rerunning it repeatedly does not automatically provide confidence. Similarly, a low-probability failure may still deserve top priority when it could expose customer data or corrupt important records.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">Regression Test Selection: Which Tests Should Run?<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><a href=\"https:\/\/bugasura.io\/blog\/regression-testing-for-efficiency\/\"><span data-contrast=\"none\">Regression test<\/span><\/a><span data-contrast=\"auto\"> selection should be based on affected behavior, risk, and the strength of the test\u2014not on ticket labels alone. The goal is to choose the smallest defensible test set that gives the team confidence in the change.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">Use this decision sequence:<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ol>\r\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"Aptos\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Run direct tests:<\/span><\/b><span data-contrast=\"auto\"> Verify the changed behavior and acceptance criteria.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"Aptos\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Add dependency tests:<\/span><\/b><span data-contrast=\"auto\"> Cover other workflows using changed functions, services, or contracts.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"Aptos\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Add high-risk regression tests:<\/span><\/b><span data-contrast=\"auto\"> Prioritize payments, access control, data integrity, and other critical product paths when relevant.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"Aptos\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Run broader suites when warranted:<\/span><\/b><span data-contrast=\"auto\"> Expand coverage for shared infrastructure, uncertain dependencies, major schema changes, or changes with a large potential blast radius.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"Aptos\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Check the release boundary:<\/span><\/b><span data-contrast=\"auto\"> Confirm that the selected tests ran against the intended build and configuration.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<\/ol>\r\n<p><span data-contrast=\"auto\">Suppose a shared validation function changes. QA might test checkout validation, saved payment method updates, and profile edits, then run a broader checkout smoke test. A full application suite may be unnecessary if the impact is well understood and the risk is low. If the dependency map is incomplete, broader testing is the safer choice.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">Automation can speed up test execution, but it cannot compensate for an incorrect selection strategy. A green pipeline only tells the team that the tests it ran passed.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">A Practical Example: One Ticket, Five Changes<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><span data-contrast=\"auto\">Imagine a ticket titled \u201cImprove checkout error messages.\u201d The pull request changes five areas:<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ul>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"2\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">Checkout validation text<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"2\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">A shared validation utility<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"2\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">An API error response<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"2\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">Logging around failed submissions<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"2\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">A common form component used in account settings<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<\/ul>\r\n<p><span data-contrast=\"auto\">QA should not treat all five changes equally. Instead, map each change to a failure mode and select tests accordingly.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<table data-tablestyle=\"MsoNormalTable\" data-tablelook=\"1696\" aria-rowcount=\"6\" aria-colcount=\"3\">\r\n<tbody>\r\n<tr aria-rowindex=\"1\">\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Change<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Risk to investigate<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><b><span data-contrast=\"auto\">Example test<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:2,&quot;335551620&quot;:2,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"2\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Error message<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Incorrect or missing feedback<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Invalid checkout input shows the expected message<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"3\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Shared validation utility<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Existing validation behavior changes<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Valid and invalid inputs work in checkout and account settings<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"4\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">API error response<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Client breaks when response structure changes<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Checkout handles expected errors without losing form data<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"5\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Logging<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Sensitive data may be recorded<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Failed submissions do not expose protected information in logs<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<tr aria-rowindex=\"6\">\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Common form component<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Unintended regression in another workflow<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<td data-celllook=\"0\"><span data-contrast=\"auto\">Account settings can still validate and save changes<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:0,&quot;335559739&quot;:0}\">\u00a0<\/span><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<p><span data-contrast=\"auto\">This is where QA adds value beyond checking whether the ticket works. It identifies how the implementation could fail elsewhere and gathers evidence around those risks.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">If time is limited, prioritize the tests with the highest potential customer or business impact. Document lower-priority coverage that remains outstanding, along with the reason for deferring it.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">Common Mistakes When Expanding Test Scope<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><span data-contrast=\"auto\">Teams often make one of four mistakes when code changes exceed the ticket.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<ul>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"3\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Testing only acceptance criteria:<\/span><\/b><span data-contrast=\"auto\"> This misses regressions introduced through shared dependencies.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"3\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Testing every connected component equally:<\/span><\/b><span data-contrast=\"auto\"> Dependency does not automatically mean meaningful risk. Prioritize based on behavior and impact.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"3\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Using the number of changed files as a risk score:<\/span><\/b><span data-contrast=\"auto\"> A small change can affect critical shared logic; a large change can be isolated.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"3\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><b><span data-contrast=\"auto\">Treating a green build as complete proof:<\/span><\/b><span data-contrast=\"auto\"> The build only validates the checks that actually ran.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<\/ul>\r\n<p><span data-contrast=\"auto\">Another mistake is failing to update the <\/span><a href=\"https:\/\/bugasura.io\/release-notes\/test-management-in-bugasura\/\"><span data-contrast=\"none\">test record<\/span><\/a><span data-contrast=\"auto\"> when scope expands. If the ticket describes one behavior but QA validates five, the rationale should be visible to reviewers and future maintainers.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">Where Bugasura Fits<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<p><span data-contrast=\"auto\">Once the test scope expands beyond the original ticket, the team needs a clear record of bugs, test cases, execution results, and outstanding risks. Keeping that information connected to the work helps QA leads explain what was verified before release and what still needs attention.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">Bugasura supports bug tracking and <\/span><a href=\"https:\/\/bugasura.io\/test-management\"><span data-contrast=\"none\">test management<\/span><\/a><span data-contrast=\"auto\">, helping teams organize bugs and test cases. Teams can explore its test management workflow to see whether it fits their process for maintaining regression coverage and recording test execution. Confirm the current feature set and workflow before relying on a specific capability.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<p><span data-contrast=\"auto\">The tool does not decide the correct test scope for you. That still requires understanding the code change, the dependencies, and the impact of failure.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<h2 aria-level=\"2\"><b><span data-contrast=\"none\">Key Takeaways<\/span><\/b><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:299,&quot;335559739&quot;:299}\">\u00a0<\/span><\/h2>\r\n<ul>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"4\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">The ticket defines the intended change; it does not define the full test scope.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"4\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">Use code change impact analysis to identify affected dependencies and workflows.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"4\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">Apply risk-based testing to prioritize failures by likelihood and impact.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"4\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">Select regression tests based on affected behavior, not just file count or ticket size.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<li aria-setsize=\"-1\" data-leveltext=\"\uf0b7\" data-font=\"Symbol\" data-listid=\"4\" data-list-defn-props=\"{&quot;335552541&quot;:1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;\uf0b7&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}\" data-aria-posinset=\"1\" data-aria-level=\"1\"><span data-contrast=\"auto\">Record test coverage, deferred checks, and remaining release risks clearly.<\/span><span data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/li>\r\n<\/ul>\r\n<h2>Frequently Asked Questions<\/h2>\r\n\r\n<div class=\"schema-faq wp-block-yoast-faq-block\">\r\n<div id=\"faq-question-1794482247408\" class=\"schema-faq-section\"><strong class=\"schema-faq-question\"><strong>1. What should QA test when a developer changes code outside the ticket scope?<\/strong>\u00a0<\/strong>\r\n<p class=\"schema-faq-answer\">QA should verify the requested behavior, investigate the additional code changes, and test dependent workflows that could regress. Ask the developer why the extra changes were necessary, then prioritize tests based on impact and likelihood of failure. If the expanded change is not understood, clarify it before signing off.<\/p>\r\n<\/div>\r\n<div id=\"faq-question-1794482267926\" class=\"schema-faq-section\"><strong class=\"schema-faq-question\">2. <strong>How does QA identify which regression tests to run?<\/strong><\/strong>\r\n<p class=\"schema-faq-answer\">Start with the changed functions, components, APIs, data structures, and configuration. Trace their dependencies, identify critical workflows, and select tests that exercise the affected behavior and likely failure modes. Use historical failures and automated impact analysis when available, but validate the selection against product and technical knowledge.<\/p>\r\n<\/div>\r\n<div id=\"faq-question-1794482284108\" class=\"schema-faq-section\"><strong class=\"schema-faq-question\">3. <strong>Does every code change require full regression testing?<\/strong><\/strong>\r\n<p class=\"schema-faq-answer\">No. Full regression testing is more appropriate when changes affect shared infrastructure, critical workflows, broad dependencies, or areas where impact is uncertain. Isolated, low-risk changes may need targeted regression and smoke testing. The decision should reflect the potential consequences of failure and how confidently the team understands the change.\u00a0<\/p>\r\n<\/div>\r\n<div id=\"faq-question-1794482312762\" class=\"schema-faq-section\"><strong class=\"schema-faq-question\">4. <strong>Who decides the final test scope: QA or the developer?<\/strong><\/strong>\r\n<p class=\"schema-faq-answer\">QA and developers should determine it collaboratively, with input from the product owner or release owner when business risk is involved. Developers explain implementation details and dependencies; QA assesses behavior and coverage gaps. Release owners help decide whether remaining risks are acceptable. No one should assume that the ticket alone defines the final scope.<\/p>\r\n<\/div>\r\n<div id=\"faq-question-1794482327414\" class=\"schema-faq-section\"><strong class=\"schema-faq-question\"><strong>5. How can teams document test scope beyond the original ticket?<\/strong><\/strong>\r\n<p class=\"schema-faq-answer\">Record the additional areas tested, the reason each area was included, the test results, and any checks deferred because of time or environment constraints. Link the evidence to the relevant ticket, bug, or test record so reviewers can understand the release decision without reconstructing the investigation from chat messages.\u00a0<\/p>\r\n<p><span class=\"TextRun SCXW247586775 BCX8\" lang=\"EN-GB\" xml:lang=\"EN-GB\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW247586775 BCX8\">Ready to organize your bugs and test cases in one workflow? <\/span><\/span><a class=\"Hyperlink SCXW247586775 BCX8\" href=\"https:\/\/my.bugasura.io\/?go=sign_up\" target=\"_blank\" rel=\"noreferrer noopener\"><span class=\"TextRun Underlined SCXW247586775 BCX8\" lang=\"EN-GB\" xml:lang=\"EN-GB\" data-contrast=\"none\"><span class=\"NormalTextRun SCXW247586775 BCX8\" data-ccp-charstyle=\"Hyperlink\">Start free with Bugasura.<\/span><\/span><\/a><span class=\"EOP Selected SCXW247586775 BCX8\" data-ccp-props=\"{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}\">\u00a0<\/span><\/p>\r\n<\/div>\r\n<\/div>\r\n","protected":false},"excerpt":{"rendered":"<p><span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\"><\/span> <span class=\"rt-time\"> 8<\/span> <span class=\"rt-label rt-postfix\">minute read<\/span><\/span>Quick answer: When a code change affects more than the ticket describes, QA should test the requested behavior, every affected dependency, critical user journeys, and any high-risk regression areas. Start with the actual code changes and their dependencies, then prioritize tests by failure impact not just by the ticket\u2019s acceptance criteria. Document the expanded scope and the risks you cannot cover.\u00a0 A ticket says, \u201cUpdate the checkout validation message.\u201d The pull request also changes a shared validation function, modifies an API response, and touches a component used by the account settings page.\u00a0 The ticket is small. The potential blast radius [&hellip;]<\/p>\n","protected":false},"author":19,"featured_media":5762,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","jetpack_post_was_ever_published":false},"categories":[139],"tags":[],"class_list":["post-5761","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-testing","post--single"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Ticket vs. Code Changes: What Should QA Test in a Release?<\/title>\n<meta name=\"description\" content=\"The ticket describes one change, but the code touched five. Learn how QA teams can spot hidden changes and decide what to test before release with confidence.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ticket vs. Code Changes: What Should QA Test in a Release?\" \/>\n<meta property=\"og:description\" content=\"The ticket describes one change, but the code touched five. Learn how QA teams can spot hidden changes and decide what to test before release with confidence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/\" \/>\n<meta property=\"og:site_name\" content=\"Bugasura Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-12T11:20:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1080\" \/>\n\t<meta property=\"og:image:height\" content=\"441\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Natasha\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Natasha\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/\"},\"author\":{\"name\":\"Natasha\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/#\\\/schema\\\/person\\\/9f7096957533f3e9f0376aa20927933e\"},\"headline\":\"The Ticket Says One Thing. The Code Changed Five Things. What Should QA Test?\",\"datePublished\":\"2026-11-12T11:20:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/\"},\"wordCount\":2133,\"image\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/bugasura.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1\",\"articleSection\":[\"Testing\"],\"inLanguage\":\"en-US\"},{\"@type\":[\"WebPage\",\"FAQPage\"],\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/\",\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/\",\"name\":\"Ticket vs. Code Changes: What Should QA Test in a Release?\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/bugasura.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1\",\"datePublished\":\"2026-11-12T11:20:24+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/#\\\/schema\\\/person\\\/9f7096957533f3e9f0376aa20927933e\"},\"description\":\"The ticket describes one change, but the code touched five. Learn how QA teams can spot hidden changes and decide what to test before release with confidence.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#breadcrumb\"},\"mainEntity\":[{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482247408\"},{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482267926\"},{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482284108\"},{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482312762\"},{\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482327414\"}],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#primaryimage\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/bugasura.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1\",\"contentUrl\":\"https:\\\/\\\/i0.wp.com\\\/bugasura.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1\",\"width\":1080,\"height\":441},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The Ticket Says One Thing. The Code Changed Five Things. What Should QA Test?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/\",\"name\":\"Bugasura Blog\",\"description\":\"Bug reporting and bug tracking solution Bugasura is a simple to use tool helping in software bug tracking, bug reporting and development. The tool is a part of the Bugasura Platform.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/#\\\/schema\\\/person\\\/9f7096957533f3e9f0376aa20927933e\",\"name\":\"Natasha\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/wp-content\\\/wphb-cache\\\/gravatar\\\/ca3\\\/ca346d352d2484e446a0ffdada46c527x96.jpg\",\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/wp-content\\\/wphb-cache\\\/gravatar\\\/ca3\\\/ca346d352d2484e446a0ffdada46c527x96.jpg\",\"contentUrl\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/wp-content\\\/wphb-cache\\\/gravatar\\\/ca3\\\/ca346d352d2484e446a0ffdada46c527x96.jpg\",\"caption\":\"Natasha\"},\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/author\\\/natasha\\\/\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482247408\",\"position\":1,\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482247408\",\"name\":\"1. What should QA test when a developer changes code outside the ticket scope?\u00a0\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"QA should verify the requested behavior, investigate the additional code changes, and test dependent workflows that could regress. Ask the developer why the extra changes were necessary, then prioritize tests based on impact and likelihood of failure. If the expanded change is not understood, clarify it before signing off.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482267926\",\"position\":2,\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482267926\",\"name\":\"2. How does QA identify which regression tests to run?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Start with the changed functions, components, APIs, data structures, and configuration. Trace their dependencies, identify critical workflows, and select tests that exercise the affected behavior and likely failure modes. Use historical failures and automated impact analysis when available, but validate the selection against product and technical knowledge.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482284108\",\"position\":3,\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482284108\",\"name\":\"3. Does every code change require full regression testing?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. Full regression testing is more appropriate when changes affect shared infrastructure, critical workflows, broad dependencies, or areas where impact is uncertain. Isolated, low-risk changes may need targeted regression and smoke testing. The decision should reflect the potential consequences of failure and how confidently the team understands the change.\u00a0\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482312762\",\"position\":4,\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482312762\",\"name\":\"4. Who decides the final test scope: QA or the developer?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"QA and developers should determine it collaboratively, with input from the product owner or release owner when business risk is involved. Developers explain implementation details and dependencies; QA assesses behavior and coverage gaps. Release owners help decide whether remaining risks are acceptable. No one should assume that the ticket alone defines the final scope.\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482327414\",\"position\":5,\"url\":\"https:\\\/\\\/bugasura.io\\\/blog\\\/what-should-qa-test-when-code-changes-beyond-the-ticket\\\/#faq-question-1794482327414\",\"name\":\"5. How can teams document test scope beyond the original ticket?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Record the additional areas tested, the reason each area was included, the test results, and any checks deferred because of time or environment constraints. Link the evidence to the relevant ticket, bug, or test record so reviewers can understand the release decision without reconstructing the investigation from chat messages.\u00a0\",\"inLanguage\":\"en-US\"},\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Ticket vs. Code Changes: What Should QA Test in a Release?","description":"The ticket describes one change, but the code touched five. Learn how QA teams can spot hidden changes and decide what to test before release with confidence.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/","og_locale":"en_US","og_type":"article","og_title":"Ticket vs. Code Changes: What Should QA Test in a Release?","og_description":"The ticket describes one change, but the code touched five. Learn how QA teams can spot hidden changes and decide what to test before release with confidence.","og_url":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/","og_site_name":"Bugasura Blog","article_published_time":"2026-11-12T11:20:24+00:00","og_image":[{"width":1080,"height":441,"url":"https:\/\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg","type":"image\/jpeg"}],"author":"Natasha","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Natasha","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#article","isPartOf":{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/"},"author":{"name":"Natasha","@id":"https:\/\/bugasura.io\/blog\/#\/schema\/person\/9f7096957533f3e9f0376aa20927933e"},"headline":"The Ticket Says One Thing. The Code Changed Five Things. What Should QA Test?","datePublished":"2026-11-12T11:20:24+00:00","mainEntityOfPage":{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/"},"wordCount":2133,"image":{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1","articleSection":["Testing"],"inLanguage":"en-US"},{"@type":["WebPage","FAQPage"],"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/","url":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/","name":"Ticket vs. Code Changes: What Should QA Test in a Release?","isPartOf":{"@id":"https:\/\/bugasura.io\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#primaryimage"},"image":{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1","datePublished":"2026-11-12T11:20:24+00:00","author":{"@id":"https:\/\/bugasura.io\/blog\/#\/schema\/person\/9f7096957533f3e9f0376aa20927933e"},"description":"The ticket describes one change, but the code touched five. Learn how QA teams can spot hidden changes and decide what to test before release with confidence.","breadcrumb":{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#breadcrumb"},"mainEntity":[{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482247408"},{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482267926"},{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482284108"},{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482312762"},{"@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482327414"}],"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#primaryimage","url":"https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1","contentUrl":"https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1","width":1080,"height":441},{"@type":"BreadcrumbList","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/bugasura.io\/blog\/"},{"@type":"ListItem","position":2,"name":"The Ticket Says One Thing. The Code Changed Five Things. What Should QA Test?"}]},{"@type":"WebSite","@id":"https:\/\/bugasura.io\/blog\/#website","url":"https:\/\/bugasura.io\/blog\/","name":"Bugasura Blog","description":"Bug reporting and bug tracking solution Bugasura is a simple to use tool helping in software bug tracking, bug reporting and development. The tool is a part of the Bugasura Platform.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/bugasura.io\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/bugasura.io\/blog\/#\/schema\/person\/9f7096957533f3e9f0376aa20927933e","name":"Natasha","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/bugasura.io\/blog\/wp-content\/wphb-cache\/gravatar\/ca3\/ca346d352d2484e446a0ffdada46c527x96.jpg","url":"https:\/\/bugasura.io\/blog\/wp-content\/wphb-cache\/gravatar\/ca3\/ca346d352d2484e446a0ffdada46c527x96.jpg","contentUrl":"https:\/\/bugasura.io\/blog\/wp-content\/wphb-cache\/gravatar\/ca3\/ca346d352d2484e446a0ffdada46c527x96.jpg","caption":"Natasha"},"url":"https:\/\/bugasura.io\/blog\/author\/natasha\/"},{"@type":"Question","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482247408","position":1,"url":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482247408","name":"1. What should QA test when a developer changes code outside the ticket scope?\u00a0","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"QA should verify the requested behavior, investigate the additional code changes, and test dependent workflows that could regress. Ask the developer why the extra changes were necessary, then prioritize tests based on impact and likelihood of failure. If the expanded change is not understood, clarify it before signing off.","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482267926","position":2,"url":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482267926","name":"2. How does QA identify which regression tests to run?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Start with the changed functions, components, APIs, data structures, and configuration. Trace their dependencies, identify critical workflows, and select tests that exercise the affected behavior and likely failure modes. Use historical failures and automated impact analysis when available, but validate the selection against product and technical knowledge.","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482284108","position":3,"url":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482284108","name":"3. Does every code change require full regression testing?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"No. Full regression testing is more appropriate when changes affect shared infrastructure, critical workflows, broad dependencies, or areas where impact is uncertain. Isolated, low-risk changes may need targeted regression and smoke testing. The decision should reflect the potential consequences of failure and how confidently the team understands the change.\u00a0","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482312762","position":4,"url":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482312762","name":"4. Who decides the final test scope: QA or the developer?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"QA and developers should determine it collaboratively, with input from the product owner or release owner when business risk is involved. Developers explain implementation details and dependencies; QA assesses behavior and coverage gaps. Release owners help decide whether remaining risks are acceptable. No one should assume that the ticket alone defines the final scope.","inLanguage":"en-US"},"inLanguage":"en-US"},{"@type":"Question","@id":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482327414","position":5,"url":"https:\/\/bugasura.io\/blog\/what-should-qa-test-when-code-changes-beyond-the-ticket\/#faq-question-1794482327414","name":"5. How can teams document test scope beyond the original ticket?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Record the additional areas tested, the reason each area was included, the test results, and any checks deferred because of time or environment constraints. Link the evidence to the relevant ticket, bug, or test record so reviewers can understand the release decision without reconstructing the investigation from chat messages.\u00a0","inLanguage":"en-US"},"inLanguage":"en-US"}]}},"jetpack-related-posts":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/bugasura.io\/blog\/wp-content\/uploads\/2026\/11\/Ticket-vs-Code-changes-scaled.jpg?fit=1080%2C441&ssl=1","post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/posts\/5761","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/comments?post=5761"}],"version-history":[{"count":0,"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/posts\/5761\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/media\/5762"}],"wp:attachment":[{"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/media?parent=5761"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/categories?post=5761"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bugasura.io\/blog\/wp-json\/wp\/v2\/tags?post=5761"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}