Testing questions

1)WhatsApp Status – Positive & Negative Test Cases
Positive Test Cases

Upload an image as status → should display correctly.

Upload a video (≤30 seconds) → should play smoothly.

Add text-only status → should be visible to contacts.

Add emojis in status → should render properly.

Status visible only to “My Contacts” → privacy works.

Status visible to “Selected Contacts” → restricted view works.

Status auto‑expires after 24 hours.

Delete status manually → should disappear immediately.

Multiple statuses uploaded → all should appear in sequence.

Status view count should update when contacts watch it.

Negative Test Cases

Upload unsupported file format (e.g., .exe) → error message.

Upload video >30 seconds → should reject.

Upload corrupted image → should fail gracefully.

Try to upload status with no internet → should queue or fail.

Upload status with empty text → should not allow.

Upload status when storage is full → should show error.

Upload status with restricted privacy → blocked users should not see.

Try to view expired status → should not be accessible.

Upload status with invalid characters in text → should handle safely.

Upload status during server downtime → should fail with error.

2)SDLC (Software Development Life Cycle)
Phases of SDLC

The Software Development Life Cycle (SDLC) is a structured process that defines how software is planned, analyzed, designed, developed, tested, deployed, and maintained to ensure quality and efficiency

3) Bug Life Cycle (Defect Life Cycle)
States of a Bug

New → Tester logs defect.

Assigned → QA lead assigns to developer.

Open → Developer starts fixing.

Fixed → Developer claims fix done.

Pending Retest → Awaiting tester verification.

Retest → Tester checks fix.

Verified → Fix confirmed.

Closed → Defect resolved.

Reopened → If issue persists after fix.

Deferred → Valid bug, postponed.

Rejected → Not a valid defect.

Duplicate → Already reported.

Key Rule: Fixed ≠ Closed. Developer marks “Fixed,” but only tester can mark “Closed” after verification.

4)Black Box Testing Techniques

Core Techniques

Equivalence Partitioning (EP): Divide inputs into valid/invalid sets.

Boundary Value Analysis (BVA): Test at edges (min, max, just inside/outside).

Decision Table Testing: Validate combinations of inputs & rules.

State Transition Testing: Check system behavior when moving between states.

Use Case Testing: Based on real-world user scenarios.

Pairwise (All-Pairs) Testing: Cover combinations efficiently.

Error Guessing: Tester intuition to predict likely defects.

Exploratory Testing: Ad‑hoc testing without predefined cases.