And Finally for now can we once some thing regarding manual testing

Manual testing:

It is a software testing process in which test cases are executed manually without using any automated tool. Here all the test cases are manually executed by the tester in the end user perspective. The difference between the actual output and the expected output is termed as defect and the test report is also prepared manually. Manual testing is done before the automation testing. And as the tester gets familiar with the application in the end user perspective, it will be useful for the tester to check all the bugs and end user’s difficulty and is also useful to write automation testing scripts.

Types of manual testing:

1. White box testing: done by developer and the code is visible is so called a white box. Checks whether the cod is written as per the standard or not.
2. Black Box testing: Done by test engineer and the code is not visible so called as Black box. Checks the functionality.
3. Grey Box testing: combination of both white box and black box. It requires requirement document to write test cases. Some of the tools used by the manual testers for manual testing are: • Jira • Jmeter • Mantis Drawbacks of manual testing:
4. It needs large number of human resources and hence needs more money resource also.
5. It is a time-consuming process.
6. Tester develops test cases based on their skills and experience. There is no evidence that they have covered all functions or not.
7. Test cases cannot be used again. Need to develop separate test cases for each new software.
8. It does not provide testing on all aspects of testing.

Some examples in support of my answer

1. Need more resources: As this involves manually testing , IT companies need skilled and trained software testers which cost them extra man power and extra cost for the support of that man power.
2. Time consuming: As the tester need to execute each test cases manually it requires more time. • Regression testing: It is not practically possible to make regression testing again and again with full perfection after each time modification is made in the program.
3. Test case efficiency: In some cases if testers overlook some test cases, or mis interoret results, or make mistake while executing test cases, the efficiency of the test case may in question. • Constraints: Due to time constraints and resource constraints it is not possible to check each and every test cases as expected so as to ensure the application is bug free.
4. Test case not reusable: As the testers need to write again and again some same kind of work they may loss interest. And make mistake even when recreating test cases. It needs more time to test.
5. All aspects of testing: not possible to perform extensive load testing and performance testing in a level of the market demand. • Load testing, stress testing: Practically it is impossible to simulate real world level load and stress level within company by using manual testing.