Which type of testing in the Software Development Life Cycle (SDLC) is…

Concept: Acceptance Testing is the SDLC phase whose defined purpose is to validate the completed software against the agreed business requirements and the applicable compliance/regulatory standards. It is usually carried out by the customer or end users (User Acceptance Testing, UAT) and acts as the final go/no-go gate before release — it answers “did we build the right product for the business?” rather than “did we build the product right?”

Application: Here the testing must verify that the software satisfies business AND compliance requirements. That is exactly the textbook role of Acceptance Testing: it runs at the end of the lifecycle, is owned by the client/end users, and includes contract, regulation and operational acceptance checks that confirm legal and business fitness before deployment.

Contrast: How the distractors differ from this purpose:

• Unit Testing — a developer checks one isolated module/function against its technical spec; it targets internal code correctness, not business fitness.

• Integration Testing — verifies that separately built modules exchange data correctly across their interfaces; a technical concern, not business validation.

• Blackbox Testing — a testing technique (testing external behaviour without seeing the code) used at many levels, not a dedicated phase for business sign-off.

• Regression Testing — re-runs existing tests after a change to confirm previously working features still work; it catches newly introduced defects, not business gaps.

Result: The testing performed to verify that the software satisfies business and compliance requirements is Acceptance Testing.