Manual testing is the process of manually testing software for defects by playing the role of an end user and using all features of the application to ensure correct behavior, following a written test plan. The document discusses various concepts in manual testing including software quality assurance, verification, validation, software life cycles, why testing is done, and different testing techniques like black box testing, white box testing, regression testing, unit testing, alpha testing, beta testing, system testing, volume testing, stress testing, and security testing.

1. g n u a l p M a o n c e t T e s t i C n Done by Vivek.v

2. What is manual testing? Manual testing is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behaviour. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases.

4. Verification:

5. Validation:

6. Software Life Cycle Models

7. Why Testing?

8. Test Life Cycle

10. Software Quality Assurance involves reviewing and auditing the software products

11. It is an activity to verify applicable procedures and standards

13. Correctness

15. It takes place after verifications are completed

16. The determination of correctness of a final program.

18. Waterfall Model – Sequential

19. Spiral Model

21. Testing comprises of set of activities to detect defects in a produced material.

22. To unearth & correct defects.

23. To detect defects early & to reduce cost of defect fixing.

24. To avoid user detecting problems.

26. To ensure that product works as user expected it to

27. To avoid user detecting problems.

29. Test Plan.

30. Design Test Cases.

31. Execute Tests.

32. Evaluate Results.

34. White Box Testing.

35. Regression Testing.

36. Unit Testing.

37. Alpha testing.

38. Beta testing.

39. System Testing.

40. Volume Testing.

41. Stress testing

42. Security testing.

44. White Box Testing Testing of a function with knowing internal structure of the program.

46. The most 'micro' scale of testing to test particular functions or code modules.

47. Typically done by the programmer and not by testers.

48. A unit can be compiled/ assembled/ linked/ loaded; and put under a test harness.

50. Testing of an application when development is nearing completion minor design changes may still be made as a result of such testing.

52. Beta Software's

53. System Testing: My name is bug *System testing is aimed at revealing bugs that cannot be attributed to a component as such, to inconsistencies between components or planned interactions between components. *Concern: issues, behaviors that can only be exposed by testing the entire integrated system (e.g., performance, security, recovery).

55. Security testing: Security testing: My Gun is Theft If your site requires firewalls, encryption, user authentication, financial transactions, or access to databases with sensitive data. you may need to test these and also test your site's overall protection against unauthorized internal or external access.