Manual Testing:

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, open-minded, resourceful, unopinionated,
and skillful.

Overview of manual testing:

Manual testing can be replaced by test automation. It is possible to record and playback manual
steps and write automated test script(s) using Test automation tools. Although, test automation tools
will only help execute test scripts written primarily for executing a particular specification and
functionality.

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.

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

What are difference between MT and AT

MT
# human will be test
#provide Input ,excute the process & validate outputs

Disadv
1.time consumption is high
2.less efficinency
3.In accurate results

AT
#tools will test

adv
1.time consumption is less
2.acuracy is veryless
3.reduction of manpower
4.reliability is high
5.over all delivery will be faster
6.cost reduction

Bug Life cycle

• bug identification
• bug logging
• bug assigninig
• bug anlaysis
• bug fixing
• bug retesting—pass or fail
• bug closure /re-opening

Fields in Bug tracking tools

1.bug id----unique numberfor every bug,generates by system
2.bug summary----differenitate about a bug in single line
3.bug description---it contain
procedure---excuting for identification of bug
expected result
actual result
screen shot
4.severity---impact of the bug on the application
5.priority---rate at which the bug has to be fixed

Status of Bug
• new
• assign
• duplicate
• answer only
• deffered
• fixed
• released
• DIT
• SIT
• UAT
• closed
• failed