1.15Question 3

Prompt: You are writing test cases for a feature with incomplete requirements. The product manager says final specs will arrive next week, but testing needs to start now. What do you do? What a strong answer should cover:

• Write test cases based on available information and assumptions
• Explicitly document assumptions in preconditions
• Focus on obvious flows (login, CRUD, error handling) that are unlikely to change
• Flag gaps and schedule a review when full specs arrive
• Use exploratory testing to supplement scripted cases Example answer:
• I would write test cases for the flows I can infer from mockups, conversations, and similar features in the product
• Each assumption gets documented: "Assumption: password minimum is 8 characters based on existing registration flow"
• I would focus first on structural behaviors (does the form submit? does validation trigger?) that are unlikely to change regardless of final specs
• Simultaneously, I would create exploratory testing charters for areas with the most uncertainty, and schedule a test case review session when the final specs land