Home » Software Testing » What is Manual testing

What is Manual testing

What is manual testing?

Manual testing is just the software testing which is normally done manually to detect bugs. In this testing, testers act as end user and try to touch all features to ensure that software is fulfilling all the requirement of Client or the need of software.

Manual testing is normally done in the initial phase of product development when is not enough stable. Once we get the stability in the functionality of software, we think about Automation of test execution.

Manual testing is gives freedom to tester for Ad-hoc testing and this increases the chances of finding more and more bugs in initial stage of software development. Manual testing is like playing with software to break it and also a chance to be familiar with all functionality of a software.

In general we can say that Manual testing is the first step of testing and automation follow it when product get stable . One more thing bigger the project, bigger the role of manual testing so we can say that manual testing have a good part in term of percentage in testing rather than automation testing, no due to its ease but also due to the cost.

Procedure involves in manual testing

1- Making a good test plan that includes all the overview,scope, methodologies and also the resources
2- Writing test cases with the help of SRS and on the basis of Use-Cases
3- Review of test cases is done to make sure that all functionalities are covered and nothing is left for writing test cases
4- Execution of test case(Dynamic testing)
5- Detecting Bugs
6- Filing bugs in Bug tracking tools like Bugzilla
7- Making test report
8- Retrospection of the whole process.

7 thoughts on “What is Manual testing”

  1. Nice posting. But in my now 2,5 years of in practial testing, I think some points of the theoretical requirements can not all be reached every time. Let me say something about the following points you said:

    Procedure involves in manual testing

    1- Making a good test plan that includes all the overview,scope, methodologies and also the resources
    –> That depends not only on you as a tester. Normaly other stakeholders (like product owner, architects, developers,…) have to help you. But depending on the project it’s not possible (missing time, missing resources, test processs not lived, …) Maybe you as a tester can estimate all this with your experience, but what if you doing tests at first time?

    2- Writing test cases with the help of SRS and on the basis of Use-Cases
    –> year, if you’re able to find or know some…In agile projects for example you will hardly find something of specification or documentation on a paper…

    3- Review of test cases is done to make sure that all functionalities are covered and nothing is left for writing test cases
    –> see point 1, same problems in practical testing possible

    4- Execution of test case(Dynamic testing)
    –> depends on your test tools (if your testprocess allowes one!)

    5- Detecting Bugs
    –> year, that’s your job as tester!

    6- Filing bugs in Bug tracking tools like Bugzilla
    –> I think that is something, which every software-company should have. A tool where someone can add findings, bugs, problems and other people can find them and fix them!

    7- Making test report
    –> Also this depends on the used test tools and methods and the defined test process (If there is one in your company!). If you do scriped based manual testing, you may execute your testcases from your tool. If you doing exploratory testing or rapid software testing for example, you are testing without script but you note your scenarios and bugs on a document or something like that…

    8- Retrospection of the whole process.
    –> Also this is something of the testprocess. It may result in statistics like “how many bugs have been found”, “how many testcases have been executed”, “how long was the time to fix the bugs”, …That all sounds good in theorie, but I’m not a freind of statistics. Who realy cares about your found bugs, about your executed and not executed testcases? The customers? I don’t beliefe that. I think the customers will find problems and bugs, which the testers could not find…especially those test scenarios which noone had ever thought about…

    KR, Ralf

    1. Its really a good explanation of these manual testing points that we normally use in Manual testing.
      This is the typical points that is the part of manual testing and testers involvement in executing test, filing bugs and also for in preparing in test report through the tool and also with their lead or manager.

      You are absolutely right that Test planning is not the task of a tester, in this normally Test manager, Test Lead and various stack-holder get involved where they try to put all kind of ingredient that should be taken in to account for giving a product with a quality.But sometime Tester also provide help in making test plan and test strategy.

      So we can say that Tester start working from very top to the bottom and he helps in making test strategy to test statistic.

      I really appreciate you effort to bring such a nice explanation to all the manual procedure that is involved in Manual testing.
      Thank to you and would be hoping more and frequent visit of yours here on my blog

  2. Pingback: Download free software testing books written by India’s most popular tester and mentor | Abode QA

  3. Pingback: Mac Beginner’s tutorial | Abode QA

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: