Manual Testing Engineer Interview Questions - 3-5 Years

Question 1

You are working on a production project and SDLC and STLC starts causing issues. How would you diagnose and fix it as a Manual Testing Engineer?

Accepted Answer

A production answer Say this first: SDLC and STLC should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply SDLC and STLC , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 2

How have you implemented test plan in a real Quality Engineering project?

Accepted Answer

A production answer Say this first: The important point about test plan is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply test plan , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 3

A release is blocked because of a problem related to test scenario vs test case. What steps would you take?

Accepted Answer

A production answer Say this first: test scenario vs test case is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply test scenario vs test case , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Choose the option that fits the workload and constraints; do not present one option as universally superior. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 4

What logs, metrics, or artifacts would you check while troubleshooting test case design techniques?

Accepted Answer

A production answer Say this first: The important point about test case design techniques is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply test case design techniques , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 5

How would you make boundary value analysis reliable enough for day-to-day production use?

Accepted Answer

A production answer Say this first: boundary value analysis should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply boundary value analysis , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 6

You are working on a production project and equivalence partitioning starts causing issues. How would you diagnose and fix it as a Manual Testing Engineer?

Accepted Answer

A production answer Say this first: equivalence partitioning should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply equivalence partitioning , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 7

How have you implemented decision table testing in a real Quality Engineering project?

Accepted Answer

A production answer Say this first: The important point about decision table testing is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply decision table testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 8

A release is blocked because of a problem related to state transition testing. What steps would you take?

Accepted Answer

A production answer Say this first: state transition testing should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply state transition testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 9

What logs, metrics, or artifacts would you check while troubleshooting smoke vs sanity testing?

Accepted Answer

A production answer Say this first: smoke vs sanity testing is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply smoke vs sanity testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Choose the option that fits the workload and constraints; do not present one option as universally superior. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 10

How would you make regression testing reliable enough for day-to-day production use?

Accepted Answer

A production answer Say this first: regression testing should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply regression testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 11

You are working on a production project and exploratory testing starts causing issues. How would you diagnose and fix it as a Manual Testing Engineer?

Accepted Answer

A production answer Say this first: exploratory testing should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply exploratory testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 12

How have you implemented ad-hoc testing in a real Quality Engineering project?

Accepted Answer

A production answer Say this first: The important point about ad-hoc testing is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply ad-hoc testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 13

A release is blocked because of a problem related to defect life cycle. What steps would you take?

Accepted Answer

A production answer Say this first: defect life cycle should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply defect life cycle , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 14

What logs, metrics, or artifacts would you check while troubleshooting bug severity vs priority?

Accepted Answer

A production answer Say this first: bug severity vs priority is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply bug severity vs priority , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Choose the option that fits the workload and constraints; do not present one option as universally superior. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 15

How would you make test data preparation reliable enough for day-to-day production use?

Accepted Answer

A production answer Say this first: test data preparation should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply test data preparation , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check SELECT COUNT(*) AS rows, MAX(loaded_at) AS freshest FROM <table>; Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 16

You are working on a production project and requirement traceability matrix starts causing issues. How would you diagnose and fix it as a Manual Testing Engineer?

Accepted Answer

A production answer Say this first: requirement traceability matrix should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply requirement traceability matrix , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 17

How have you implemented API testing basics in a real Quality Engineering project?

Accepted Answer

A production answer Say this first: The important point about API testing basics is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply API testing basics , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 18

A release is blocked because of a problem related to database testing basics. What steps would you take?

Accepted Answer

A production answer Say this first: database testing basics should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply database testing basics , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check SELECT COUNT(*) AS rows, MAX(loaded_at) AS freshest FROM <table>; Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 19

What logs, metrics, or artifacts would you check while troubleshooting mobile testing basics?

Accepted Answer

A production answer Say this first: The important point about mobile testing basics is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply mobile testing basics , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 20

How would you make cross-browser testing reliable enough for day-to-day production use?

Accepted Answer

A production answer Say this first: cross-browser testing should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply cross-browser testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 21

You are working on a production project and Agile testing starts causing issues. How would you diagnose and fix it as a Manual Testing Engineer?

Accepted Answer

A production answer Say this first: Agile testing should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply Agile testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 22

How have you implemented shift-left testing in a real Quality Engineering project?

Accepted Answer

A production answer Say this first: The important point about shift-left testing is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply shift-left testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 23

A release is blocked because of a problem related to test closure report. What steps would you take?

Accepted Answer

A production answer Say this first: test closure report should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply test closure report , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 24

What logs, metrics, or artifacts would you check while troubleshooting risk-based testing?

Accepted Answer

A production answer Say this first: The important point about risk-based testing is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply risk-based testing , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. Start with containment and evidence. Changing several variables at once makes the incident harder to understand. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Question 25

How would you make UAT support reliable enough for day-to-day production use?

Accepted Answer

A production answer Say this first: UAT support should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working. Use a real scenario Imagine a checkout flow changed by several teams in the same release. The team must decide how to apply UAT support , verify the result, and explain the user impact. For a Manual Testing Engineer, attach the explanation to a risk-based test plan and failure report. Show judgment describe the implementation path, the main trade-off, and the evidence you would collect. State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership. Call out false confidence from brittle automation and the control that reduces it. Concrete check npm test -- --runInBand Evidence to mention Track escaped defects, flaky-test rate, and feedback time . Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up. Practice prompt: Use a checkout flow changed by several teams in the same release as the example and show where you would stop a risky rollout.

Real implementation, debugging, tools, logs, edge cases, and measurable fixes.

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check

Evidence to mention

A production answer

Use a real scenario

Show judgment

Concrete check