Manual Testing Online Training

Manual Testing – Process Lifecycle

Manual Testing is a process of finding out the defects, bugs in a software program. A tester perform end user role and verifies if all the features are working properly or not. Tester manually executes the test cases. Manual testing is the process of using the features of an application as an end-user. With manual testing, a tester manually conducts tests on the software. This process is carried out to find defects/bugs. Manual Testing is a basic type of testing in the application under test.

Software testing process flow

Requirement (SRS Review/Analysis)

A software requirements specification (SRS) is a document that contains complete description about how the system is expected to perform. After completing, it is signed off at the end of requirements. SRS review is nothing but going through the functional requirements specification document and trying to understand what the target application is going to be like.

Test Plan Creation

It’s a document developed by test manager. It is set of ideas that guides and is created to inform all the managers, testers, developer about the testing process.

Test plan contains detailed understanding of workflow. It consist test templates which has introduction, scope, test strategy, environment requirements, test schedule, functions to be tested, resources and responsibilities, deliverables, suspension/ exit criteria, resumption criteria, dependencies, risks, tools, documentation and approvals.

• Create a matrix environment where the software can be tested in all environments.
• Configure the test setups for Win 7, Win 8, Win 10 and Android
• Keep the databases (MySQL, Oracle, SQLServer) in the test matrix in such a way that they are too integrated with some test.

In manual testing, a product is checked against non-practical and utilitarian prerequisites manually, usually supervised by a quality affirmation group.

This method involves a bit of beta-testing, like running the application on various gadgets to discovering possible deviations from the initial prerequisites. The quality group uses some redefined test cases to measure quality, keeping a watchful eye on any possible blunders or defects with the application’s utility, UX, and outline.
 

Manual Testing Activities

Requirements Analysis:

 This is where the analyzers familiarize themselves with the app’s details so as to identify any errors.

Test Cases Creation:

  With the useful details in hand, the testing group begins a series of experiments on the item, covering every real component and plan components inside the product.

Conducting the Tests:

 Tests are carried out one after the other, armed with a good understanding of the product and how it operates. 

Logging Bug Reports:

 As the tests are conducted, the existing bugs and blunders are noted, logged, and presented in a detailed report including recommendations for remediation.

Pros:

Manual testing is Consistent with Life Testing

Manual testing seeks to use the product in a perceived real-time, mirroring the exact environment in which the application will be utilized. As a result, a preventative discovery of potential bugs or blemishes can be identified prior to the client launching the application.

Exhaustive Plan Audit 

Obviously, an automated system can not offer criticism regarding the application’s look and feel, unlike a cognitive, real-life perspective. An individual’s honest feedback about the physical qualities of the application is usually thorough and insightful.

Cost Effectiveness

When it comes to additional device usage, the manual testing process saves resources. Also, no pre-requisites, certifications, or discernment applies to the candidate(s) interested in performing the review – anyone can do it. Friends and colleagues, for instance, could be enlisted to perform quality checks.

Expanded Adaptability

With manual testing, there is the flexibility advantage where adjustments can be done quickly and on the go.