Sanity Testing

- Sanity test is done during the release phase to check for main functionalities of the applciation without going deeper.

- Sanity testing was performed when  receiving software build (with some minor changes) from the development team.

- Sanity testing also ensures that the modification in the code or functions does not affect the associated modules.

- Sanity testing is performed by testers alone.

- Sanity testing , build is relatively stable.

- It is done on stable build.

- it is part of regrassion testing.

- it is planned when there is no enough time to do in depth testing.

- Typically , in sanity testing does not involve documentation.

- Sanity testing also validates the accuracty of the newly added features and modules.

• Sanity Testing process

1. Identification

2. Evaluation

3. Testing