Supporting track

Manual Testing

The fundamentals interviewers still probe before automation questions.

What this track covers

SDLC & STLCTest case design techniquesBoundary value analysisEquivalence partitioningDefect lifecycleSeverity vs priorityRisk-based testingExploratory testingRegression vs retesting

Severity vs priority

Severity is technical impact; priority is business urgency. They move independently.

Why it is required: A guaranteed warm-up question, and a bad answer signals weak fundamentals.

Example: Company logo misspelled on the homepage: low severity, highest priority.

text

1High severity / Low priority  → crash in a feature used once a year
2Low severity  / High priority → typo in the company logo on the landing page
3High severity / High priority → checkout payment fails for all users
4Low severity  / Low priority → tooltip text truncated on an admin screen

Expected result

Four quadrants with a concrete example each.

Common mistakes

Treating them as synonyms
Only giving textbook definitions with no example

Give an example of a high-severity, low-priority defect.