MANUAL TESTING DEFINATIONS

1.Quality: - It is defined as the conformance to the customer specification.

2.Testing: - A Tester should suppose to identify the defects.

3.White box testing: -Based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions.

4.Test case: - Test case is a description of what to be tested, what data to be given and what actions to be done to check the actual result against the expected result.

5.Black box testing: - Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.

6.Functionality testing: - Testing whether the functionality of the application is working or not and whether all the requirements have covered are not.

7.System testing: - The entire application tested according to the requirements.

8.Sanity testing: - Initial testing conducted on the application to check the proper behavior on the application.

9.Smoke testing: - Initial testing is conducted on over all application to check whether all the functionalities available to conduct detail testing on them.

10.Regression testing: - Retesting the bug after fixing or any modifications or enhancement done to the application and testing whether the existing functionalities are effecting to the privies functionalities or not.

11.Integration testing: - All the modules are integrated together and testing how modules are couple together and communication between the modules.

12.Usability testing: - Checking whether it is user friendliness or not.

i.      To check for the look and feel of application.

ii.  Where the end user can understand and can easily use the application.

13.User acceptance testing: - After all the bugs are fixed we have to test once again to make shore that the application meets the user requirements.

14.Severity: - how much the bug is effecting the application.

15.Priority: - When the bug is to be fixed.

16.Unit testing: - After completion of their reviews, programmer concentration on coding, to physically construct a soft ware. In this level, their will test every program through white box testing.

17.Recovery testing: - It is also known as reliability testing during this test, testing engineers validates that whether our application build change from abnormal state to normal state or not.

18.Compatibility testing: - It is also known as portability testing. During this test, testing engineer validates that whether our application build run on customer expectation platform or not.

19.Configuration testing: -It is also known as hardware compatibility testing. During this test testing engineer validates that whether our application support different technology hardware devises or not.