Verification

Verification assesses development-phase procedures to see if they adhere to user requirements. For example, static testing is verification. Before validation, verification testing is carried out. It is not related to running the code. It entails tasks including desk checks, walkthroughs, inspections, and reviews. Before the development cycle, the bugs are discovered. It complies with the standards outlined in the SRS paper.

The QA team provides verification, ensuring that the program complies with the specifications as down in the SRS document.

Validation

Validation evaluates the product to ensure it satisfies requirements after the development phase, and after verification.

It uses techniques like non-functional testing, white box testing, and black box testing. The bugs are discovered after the development cycle. It determines whether or not it satisfies the requirements.

Regression

• Regression testing is a type of analysis used to determine whether recent code changes have had an impact on previously unaffected features.
• Regression testing’s primary goal is to ensure any code modifications cannot negatively affect functionalities already in place.
• General testing; it may be carried out whenever there are code changes.
• On the test cases that passed, it was executed.
• Regression testing can be automated, although manual testing is more expensive and time-consuming.
• Regression testing does not include defect verification.
• Regression testing is carried out concurrently with retesting, depending on the resources that are available.

Retesting

• Retesting entails testing modules that were unsuccessful during the previous run.
• Retesting is performing testing on already corrected flaws.
• Planned; not spontaneous.
• Cannot be automated
• Includes defect verification.
• Always performed after retesting because retesting has a higher priority.