Regression Testing:

Checking that the previously working modules of the applications are working fine after any code of the application have been modified, changed or enhanced.

Retesting :

Checking that the previously reported non-working modules of the application are working fine after the bugs have been fixed.

User Acceptance Testing :

User Acceptance Testing (UAT) is done by the client to accept the application with predefined function and non functionality given in the Software Requirement Specifications (SRS).

It is actually selecting the Major functional and non functional test cases and testing with an application at client side or end user side.

Under UAT three different kinds of testings are there.

1.  Alpha Testing
2. Beta Testing
3. Usability Testing

Alpha Testing :

It is done by client at the development side or in the presence of developers , when a project is closer to the completion. If a design change needs to be done ,it can be done at this level.

Beta Testing :

This testing is done at client end in the absence of developers or development side ,after the project has been completed. In this no design changes can be done, only bugs can be fixed and the application can be re tested.

Usability Testing :

Checking the user friendliness of the application, i.e. the end user is comfortably handling the application (Checking for the Help files, release notes, information about versions)

ERROR (Developers) :-

A discrepancy (mismatch) between a computed, observed or measured value and and the specified or theoretically correct value is called an ERROR.

BUG (Tester):-

A fault in a program which causes the program to perform in an unintended or unanticipated manner is called as BUG.

FAILURE (Developers) :-

An inability of a system or a component to perform its required function within specified performance requirement is called a FAILURE.

FAULT (Developers) :-

An incorrect step or a process in a computer program which causes the program to perform in an unintended or un anticipated manner is called FAULT.

Testing Methodology and Definition :-

Test Environment : –

The Hardware and Software environment or any other third party software to which the software or application under test , interacts when the testing is carried out is called “Test Environment”.

Test Suit :-

The test suit is collection of test cases used to validate the behavior of the product. The scope of the test suit is varies from organization to organization.

Test Driver (or) Test Hardness :-

It’s a program or test tool used to execute test cases is called Test Driver.

Test Bed :-

An execution environment configure for testing is called Test Bed. It may consists of specific hardware, software,OS and network topology in which testing is carried out.

Test Scenario :-

A test scenario is set of test cases that ensures, a particular business process or functionality are tested from end to end.

Positive Test Scenario :-

Set of test cases , which  attempts to show there are particular function or method does what it supposed to do.

Negative Test Scenario :-

Set of test cases , which attempts to show that there are particular function or module does, what it not supposed to do.

Test Strategy :-

Testing strategy is used to point out test factors or risk involved in each phase of development life cycle and process to reduce those risks.

Test Log :-

A chronological record of all relevant details about the execution of test cases or test procedures.

Test Report :-

A document describing the conduct and result of the testing carried out for a system.