Learn Manual Testing:
Manual testing is performed by the tester who carries out all the actions
on the tested application manually, step by step and indicates whether a
particular step was accomplished successfully or whether it failed.
Manual testing is always a part of any testing effort. It is especially
useful in the initial phase of software development, when the software and its
user interface are not stable enough, and beginning the automation does not make
1) Writing Test Cases by using SRS, FRS and use case documents
2) Reviewing Test Cases
3) Executing Test Cases
4) Finding & Reporting Bugs
5) Getting it Fixed
Pros of Manual
If the test case only runs twice a coding milestone, it most
likely should be a manual test. Less cost than automating
It allows the tester to perform more ad-hoc (random testing).
In my experiences, more bugs are found via ad-hoc than via automation.
And, the more time a tester spends playing with the feature, the
greater the odds of finding real user bugs.
Cons of Manual
Running tests manually can be very time consuming
Each time there is a new build, the tester must rerun all
required tests - which after a while would become very mundane and tiresome.
Difference between Manual Testing and
1.What if the software is so buggy it can't really be tested at
2.What's a 'test case'?
3.How testing is proceeded when SRS or any other document is not given?
4.why does software have bugs?
5.What is memory leaks and buffer overflows ?
Because time is valuable, we deliver quick and easy learning. At KabInfo.Net,
you can study everything you need to learn, in an accessible and handy format.
"No One Is Great, And Every One Is GREAT"
Tester : "I Delivered a 100% Bug Free Product!"
KabInfo.Net - Testing School is for self training only. We do not warrant the
correctness of the content. The risk of using it remains entirely with the user.
While using this site, you agree to have read and accepted our
. All Rights Reserved.
Logo Courtesy - Venkat Battu