Which sequence best describes a basic testing methodology?

Which sequence best describes a basic testing methodology?

• A. Create test cases, define scope, execute tests, log defects, report.
• B. Define scope, execute tests, write a test plan, log defects, report.
• C. Define scope, write a test plan, create test cases, execute tests (manual/automation), log defects, retest, report.
• D. Define scope, write a test plan, log defects, create test cases, execute tests.

Answer: (C)

A basic testing methodology follows a logical flow from planning to delivery: start by defining what will be tested and what quality goals are, then plan how to test, design concrete test cases, execute them (manually or with automation), log any defects found, retest after fixes, and finally report the results. Defining the scope sets boundaries and objectives so you know what’s in and out of scope. Writing a test plan documents the approach, resources, environment, schedule, and entry/exit criteria, giving the team a clear roadmap. Creating test cases translates that plan into concrete steps and expected results, ensuring you systematically verify the intended functionality. Executing tests puts those cases into action, and logging defects captures the details needed to reproduce and fix issues. Retesting after fixes confirms the defects are resolved and no new problems were introduced. Reporting communicates test progress, quality status, and risk to stakeholders. The other sequences skip essential pieces or place steps in illogical order—for example, designing test cases after execution, or logging defects before test cases exist, or missing retesting and final reporting—so they don’t reflect a complete, disciplined workflow.

A basic testing methodology follows a logical flow from planning to delivery: start by defining what will be tested and what quality goals are, then plan how to test, design concrete test cases, execute them (manually or with automation), log any defects found, retest after fixes, and finally report the results.

Defining the scope sets boundaries and objectives so you know what’s in and out of scope. Writing a test plan documents the approach, resources, environment, schedule, and entry/exit criteria, giving the team a clear roadmap. Creating test cases translates that plan into concrete steps and expected results, ensuring you systematically verify the intended functionality. Executing tests puts those cases into action, and logging defects captures the details needed to reproduce and fix issues. Retesting after fixes confirms the defects are resolved and no new problems were introduced. Reporting communicates test progress, quality status, and risk to stakeholders.

The other sequences skip essential pieces or place steps in illogical order—for example, designing test cases after execution, or logging defects before test cases exist, or missing retesting and final reporting—so they don’t reflect a complete, disciplined workflow.