Ideally in which phase of Developement Testing should be started?
-
Developement phase
-
Design Phase
-
Requirement gathering phase
-
Intergration phase
Testing should ideally begin during the requirement gathering phase using the 'shift-left' approach. This allows test planning, identification of testable requirements, and test case design before development starts, reducing cost and rework effort.
Best practice (and a core testing principle) is to start testing activities as early as possible — during requirements gathering — so that ambiguous, incomplete, or incorrect requirements are caught before they propagate into design and code. Waiting until the development or integration phase to start testing means defects introduced early are found much later, when they're far more expensive to fix.