Manual Testing
Manual Testing
Software testers employ black-box testing when they do not know the internal architecture or
code structure. The techniques are:
Equivalence Partitioning
Cause-effect graphing
Unlike black-box testing, white box involves analyzing the system’s internal architecture and/or
its implementation, in addition to its source code quality. It’s techniques are:
Statement Coverage
Decision Coverage
Alpha testing is at the developer’s site before release. Potential clients conduct beta testing at
their websites.
Sanity testing is testing done at the release level to test the main functionalities. It’s also
considered an aspect of regression testing.
Unit/component/program/module testing
Integration testing
System testing
Acceptance testing
A bug is a fault in the software that’s detected during testing time, while a defect is a variance
between expected results and actual results, detected by the developer after the product goes live.
If a program can’t run or be compiled during development, it’s an error. If an end-user discovers
an issue with the software, it’s a failure.
This tests the interface between the software and the end-user. Short for Graphics User Interface.
Software testing is required to ensure the quality and reliability of a software product.
Testing helps to uncover any bugs, errors, or other issues in the software so that they can be
addressed and fixed before the product is released.
Testing also ensures that the software meets all the requirements specified by the customer
and works as expected.
10. What are the different levels of manual testing?
Unit Testing
Integration Testing
System Testing
Performance Testing
Security Testing
Compatibility Testing
Usability Testing
Installation Testing
Smoke testing
Sanity testing
Regression Testing
Manual testing is a process of identifying bugs and errors in a software product without the use
of automated tools. The procedure for manual testing is as follows:
Identify the scope of testing: The first step of manual testing is to identify the scope of testing.
The range could be a specific module, functionality, feature, or end-to-end system.
Design test cases: The next step is to design test cases based on the identified scope. The test
cases should include test scenarios, data, expected results, and all other details necessary to
perform the tests.
Execute the test cases: After designing the test cases, the testers execute them to find any
discrepancies between the expected and actual results.
Record the results: While performing the tests, the testers should record the results for further
analysis.
Documentation is an integral part of manual testing. It is essential to document all steps taken in
the testing process to ensure thorough test coverage and accurate results. Documentation
provides an audit trail, which can be used to evaluate past test results and identify areas for
improvement. Additionally, it is a reference for other testers who may be unfamiliar with the
system or application under test.
1. Functional testing
2. Non-Functional testing
It checks the software against the functional requirements or specification, ignoring non-
functional characteristics like performance, usability, and dependability.
The purpose of functional testing is to ensure that the software up to snuff in terms of
functionality and to solve the difficulties of its target users.
Unit Testing
Integration Testing
Regression Testing
System Testing
Smoke Testing
Performance Testing
Stress Testing