Environment & Code Flow
If a fix is deployed to Stage but not yet to Prod, where should QA validate the bug fix?
QA should validate in Stage (Pre-Prod)
When does UAT normally take place in the release cycle?
UAT happens after QA sign-off in Stage/Pre-Prod and before Production deployment.
A spelling mistake is found on the “Contact Us” page in Prod. What severity and SLA applies?
It is a Cosmetic defect and can be fixed in the next sprint.
A new "Back to top" feature was released, but it is not working. How should QA classify it?
Functional Defect - as it is new feature and not working as per requirement
Tobacco preferences is not working in stage and QA found issue in regression. Release is in 5 days, Should it be :
1. S1, P1
2. S2, P2
3. S1, P2
4. S2, P1
Can Prod code ever be promoted back into Stage after go-live?
No. Code promotion always flows forward (QA → Stage → Prod), generally not backward.
Who is responsible for conducting UAT and giving the final go-ahead for Prod release?
Business users or client representatives conduct UAT and provide the sign-off.
Can a Production defect be scheduled for 15 days later in the next sprint?
Yes for cosmetic and NO for P1 and P2s
The “Forgot Password” link worked fine before, but after login changes in the last release, it no longer works. How should QA classify it?
Regression defect — a previously working feature broke due to new changes.
A spelling mistake is found deep inside a help page in production. Should it be:
1. S3, P2
2. S1, P4
3. S4, P1
4. S4, P4
A tester says: “It worked yesterday in Stage, but today without any deployment it’s broken.” What is the most likely cause?
The cause is likely environment, configuration, or data issue — not a code change.
Will UAT perform testing in Stage after Production go-live? Why or why not?
No, because UAT is a pre-Prod activity for sign-off. After go-live, validation happens in Prod, not back in Stage.
After Prod deployment, a non-critical defect is found. QA marks it as P3 and assigns to backlog. Business insists it should be fixed immediately. Which one is correct — SLA or business priority?
Business priority overrides. Even if severity is low, priority can be high. SLA must be adjusted accordingly.
A bug is discovered in Prod on the page, where images have been broken for months. No one tested this page before. How should QA classify it? Lets say its a non-authoring bug
Existing defect — the issue always existed, just never tested.
If a defect is Severity High, Priority should also be High. why or why not? Explain?
No. Severity = impact of the bug (technical seriousness), Priority = urgency of fix (business decision). A bug can be High severity but Low priority (rarely used feature), or Low severity but High priority (visible typo on home page).
A developer deployed a fix to Stage only. The tester checks in Prod, sees the bug still there, and reopens it. What mistake did QA make?
QA tested in the wrong environment (Prod instead of Stage) where the fix was actually deployed.
A tester says, “The UAT team will re-test the bug on Prod after go-live.” What’s wrong with this statement?
UAT is never done on Prod. After go-live, only sanity testing or business validation in live environment occurs, not UAT.
A registration fails only in Prod due to a 3rd-party integration issue, while Stage works fine. How should QA classify and escalate it?
QA should classify it as a P1 Production incident, mark it as an environment/integration issue, and immediately escalate to 3rd-party vendor for resolution.
A feature went live 15 days ago. Now a bug is found in Prod, and it’s reproducible in Stage too. QA never tested this scenario earlier. How should QA classify it?
Functional defect with a QA miss, because the feature never worked correctly and wasn’t validated.
A Prod issue causes the “Contact Us” page to be down. Should it be High severity and Low priority since it’s not core business flow?
1. S1, P1
2. S1, P4
3. S2, P3
4. S2, P1
Stage and Prod are running on the same code version. In Stage, a feature works, but in Prod the same feature fails. What does this indicate?
It indicates an environmental difference (such as config, data, cache, or integration settings), not a code issue.
UAT signed off on Stage and the release went live. In Production, a critical issue is found by end-users. Who owns the responsibility for this miss — QA team or UAT team?
The QA team owns responsibility if the defect was due to missing coverage or poor regression testing. The UAT team owns responsibility if the defect was clearly outside documented requirements but still signed off. In reality, responsibility is shared — QA for missed validations, and UAT for business sign-off.
A severe Prod issue is reported at 3 AM. QA cannot reproduce in Stage or QA env. Business impact is huge. Should QA proceed to log a defect without reproducing it before logging?
Yes.All Prod issues must be logged immediately as incidents with full evidence (logs/screenshots). Root cause must be analyzed later. Waiting risks SLA breach
A defect is reported in Prod for a field that accepts invalid characters. QA finds the same bug in Stage and confirms that no recent changes were made in that area. How should QA classify it?
Existing defect — it always existed but was never caught earlier.
A small typo in the name of company appears on the home page in Prod. What is the severity and priority?
1. S2, P1
2. S1, P1
3. S4, P4
4. S4,P1