- Manual Testing is a type of Software Testing where Testers manually execute test cases without using any automation tools.
- Manual Testing is the most primitive of all testing types and helps find bugs in the software system.
- Any new application must be manually tested before its testing can be automated. Manual Testing requires more effort, but is necessary to check automation feasibility.
- Manual Testing does not require knowledge of any testing tool.
- Manual Testing is a process of finding out the defects or bugs in a software program. In this method the tester plays an important role of end user and verifies that all the features of the application are working correctly. The tester manually executes test cases without using any automation tools. The tester prepares a test plan document which describes the detailed and systematic approach to testing of software applications. Test cases are planned to cover almost 100% of the software application. As manual testing involves complete test cases it is a time consuming test.
- The key concept of manual testing is to ensure that the application is error free and it is working in conformance to the specified functional requirements.
- Test Suites or cases ,are designed during the testing phase and should have 100% test coverage.
- It also makes sure that reported defects are fixed by developers and re-testing has been performed by testers on the fixed defects.
- Basically, this testing checks the quality of the system and delivers bug-free product to the customer.
Procedure of Manual Testing
Given below are the details of each testing step that is carried out in each software quality and testing life cycle specified by IEEE and ISO standards:
1) SRS Review: Review of the software requirement specifications
2) Objectives are set for Major releases
3) Target Date planned for the Releases
4) Detailed Project Plan is built. This includes the decision on Design Specifications
5) Develop Test Plan based on Design Specifications
6) Test Plan: This includes objectives, the methodology adopted while testing, features to be tested
and not to be tested, risk criteria, testing schedule, multi-platform support and the resource allocation for testing.
7) Test Specifications:This document includes technical details (Software requirements) required prior to testing.
8) Writing of Test Cases
Smoke (BVT) test cases
Sanity Test cases
Regression Test Cases
Negative Test Cases
Extended Test Cases
9) Development – Modules are developed one by one
10) Installers Binding: Installers are built around the individual product.
11) Build procedure :A build includes Installers of the available products – multiple platforms.
12) Testing Smoke Test (BVT): Basic application test to take decision on further testing
- Testing of new features
- Cross-browser and cross-platform testing
- Stress testing and memory leakage testing.
13) Test Summary Report Bug report and other reports are created
14) Code freezing No more new features are added at this point.
15) Testing Build and regression testing.
16) Decision to release the product
17) Post-release scenario for further objectives.
Comments
Post a Comment