Manual Testing

Manual Testing

Manual Testing

Manual Testing is the process in which a quality analyst manually tests a software application in order to identify bugs. Quality Analyst is generally required to analyse the performance of website and mobile applications from end user's point of view. Quality analyst verifies the actual behaviour of software against expected behaviour and if there's any difference that's called bug.

Example: A developer has created a website and wants to test it for functionality. Here expected behaviour is that user must be able to enter username and password and submit the credentials by clicking on login button. Suppose the login button doesn’t redirect to home page. In such a case It is called bug. Quality Analyst (QA) will report this bug to the developer.

  • It is an essential part of any test scheme/strategy as it helps QA gain deeper knowledge from an end user’s perspective.
  • Manual testing is done or carried out by human without using any kind of test automation tools. It judges software from the User’s Experience.
  • Stages of Manual Testing

    1. Unit Testing: It is often used by developers to discover bugs in the early stages of the development cycle. It involves verification of individual components or units of source code.
    2. For example: It is generally like clicking a button on a web page and verifying whether it performs the desired operation.i.e ensuring that a share button on a webpage lets you share the correct page link or go to the correct destination.

    3. Integration Testing: It comes after unit testing. This approach helps Quality Analyst (QA) evaluate how several components of the application work together to provide the desired result. It is a systematic technique for verifying the software structure and sequence of execution while conducting tests to uncover errors associated with interfacing.
    4. System Testing: It is defined as testing of a complete and fully integrated software verifies that an application performs tasks as designed.
    5. Acceptance Testing: It is done to verify whether the system as a whole is fit for use in the real world. It is performed both internally and externally .Alpha and Beta Testing are two types of Acceptance Testing.

    Alpha testing is done by the members within the organization.

    Beta Testing is done by a limited number of actual end users.

    This approach helps the team to evaluate how well the product satisfies the user’s standards. It also identifies bugs at last stage before Product Releasing.

    Here’s How to Perform Manual Testing Step by Step:

  • Analyse requirements from the Software Requirement Specification document (SRS).
  • Create a clear test plan.
  • Get test cases reviewed by the QA lead.
  • Execute test cases and detect any bugs.
  • Report bugs, if any, and once fixed, run the failed tests again to re-verify the fixes.
  • Manual testing is used to find bugs, faults and flaws in a software product. Some of the Manual Testing tools are Bugzilla , JIRA, JMETER etc.

    I Hope you enjoy this blog

    Thank You

    Want a Team that Delivers Result ? Connect now with us.


    Our Offices


    F-429, Phase 8B, Industrial Area, SAS Nagar, Punjab 160059

    +91 82198-18163


    13506 Summerport Village Pky Suite 355 Windermere, FL 34786

    +1 (321) 900-0079


    15 Meltwater Cres, Brampton L6P3V8

    +1 (647) 892-6147