SlideShare a Scribd company logo

Manual testing

•Download as DOCX, PDF•
•
S
sephalika

Manual testing is the oldest and most rigorous type of software testing that requires a tester to perform manual test operations without automation help. It is a laborious process requiring patience and other qualities from testers. A manual tester would typically understand functionality, prepare a test environment, execute test cases manually, verify results, record pass/fail, summarize results in a report, publish the report, and record any new defects found. While manual testing is thorough, test automation has become necessary due to shorter deadlines, but manual testing remains crucial and cannot be completely substituted.

Related slideshows

Test case management
Test case managementTest case management
Test case management
 
Data handling and constraints
Data handling and constraintsData handling and constraints
Data handling and constraints
 
softwaretestingppt-FINAL-PPT-1
softwaretestingppt-FINAL-PPT-1softwaretestingppt-FINAL-PPT-1
softwaretestingppt-FINAL-PPT-1
 
1 of 3
Manual testing is the oldest and most rigorous type of software testing. Manual testing requires a tester to perform manual test operations on the test software without the help of Test automation. Manual testing is a laborious activity that requires the tester to possess a certain set of qualities; to be patient, observant, speculative, creative, innovative, openminded, resourceful, unopinionated, and skillful. Steps for Manual Testing A manual tester would typically perform the following steps for manual testing: 1. Understand the functionality of program 2. Prepare a test environment 3. Execute test case(s) manually 4. Verify the actual result 5. Record the result as Pass or Fail 6. Make a summary report of the Pass and Fail test cases 7. Publish the report 8. Record any new defects uncovered during the test case execution There is no complete substitute for manual testing. Manual testing is crucial for testing software applications more
thoroughly. Test automation has become a necessity mainly due to shorter deadlines for performing test activities, such as regression testing, performance testing, and load testing. HOW TO USE: Process evaluated in all segments of SDLC. Execution of the can be done in conjunction with normal system testing. Instead of preparing, execution and entering actual test transactions the clerical and supervisory personnel can use the results of processing from application system. To test people it requires testing the interface between the people and application system. WHEN TO USE: Verification that manual systems function properly should be conducted throughout the SDLC. Should not be done at later stages of SDLC. Best done at installation stage so that the clerical people do not get used to the actual system just before system goes to production. Example: Provide input personnel with the type of information they would normally receive from their customers and then have them transcribe that information and enter it in the computer. Users can be provided a series of test conditions and then asked to respond to those conditions. Conducted in this manner, manual support testing is like an examination in which the users are asked to obtain the
answer from the procedures and manuals available to them. Usage: It involves testing of all the functions performed by the people while preparing the data and using these data from automated system.

More Related Content

Manual testing

  • 1. Manual testing is the oldest and most rigorous type of software testing. Manual testing requires a tester to perform manual test operations on the test software without the help of Test automation. Manual testing is a laborious activity that requires the tester to possess a certain set of qualities; to be patient, observant, speculative, creative, innovative, openminded, resourceful, unopinionated, and skillful. Steps for Manual Testing A manual tester would typically perform the following steps for manual testing: 1. Understand the functionality of program 2. Prepare a test environment 3. Execute test case(s) manually 4. Verify the actual result 5. Record the result as Pass or Fail 6. Make a summary report of the Pass and Fail test cases 7. Publish the report 8. Record any new defects uncovered during the test case execution There is no complete substitute for manual testing. Manual testing is crucial for testing software applications more
  • 2. thoroughly. Test automation has become a necessity mainly due to shorter deadlines for performing test activities, such as regression testing, performance testing, and load testing. HOW TO USE: Process evaluated in all segments of SDLC. Execution of the can be done in conjunction with normal system testing. Instead of preparing, execution and entering actual test transactions the clerical and supervisory personnel can use the results of processing from application system. To test people it requires testing the interface between the people and application system. WHEN TO USE: Verification that manual systems function properly should be conducted throughout the SDLC. Should not be done at later stages of SDLC. Best done at installation stage so that the clerical people do not get used to the actual system just before system goes to production. Example: Provide input personnel with the type of information they would normally receive from their customers and then have them transcribe that information and enter it in the computer. Users can be provided a series of test conditions and then asked to respond to those conditions. Conducted in this manner, manual support testing is like an examination in which the users are asked to obtain the
  • 3. answer from the procedures and manuals available to them. Usage: It involves testing of all the functions performed by the people while preparing the data and using these data from automated system.