Manual Testing Introduction and Test Processes
Manual testing is the process of manually testing an application to find bugs without using tools or automation. Test phases are run by humans without scripting support.
Manually testing for bugs or vulnerabilities in a software test is an important part of software testing. Software testers use and review the software as the end user uses it. The testing process is a systematic process that uses test plans and scenarios. Manual testing primarily examines and tests a website from an end-user perspective. Manual testing is done by software developers/testers using their knowledge and experience to identify bugs within software.
Advantages of Manual Testing
Automation tests can not find faults that are not coded in detail, testing can be done to the extent that the rules are given. At this point, it is impossible to automate and test all user experiences. Manual testing finds user issues more accurately and usability testing can only be done manually.
Tester feedback and experiences are is very important. It is much easier to keep up with changing scenarios with manual testing. If the application and scenarios change frequently, manual testing will be both easier and less costly. Changing automation scenarios will take more time. It is quite common to encounter another bug while testing a bug.
In these cases, when performing Manual testing, functions other than the tested scenario can also be quickly tested. Manual testing costs less as automation tools and processes are not required.
Stages of Manual Testing
- Requirement Analysis
- Test Plan Creation
- Test case Creation
- Test case Execution
- Bug Logging
- Bug Fix & Re-Verification
Requirement Analysis
In this phase of the Software Testing Life Cycle, the prerequisites are reviewed and analyzed. Brainstorming is also done with different teams and it is checked whether the project requirements are clear. This phase helps to identify the test product.
Test Plan Creation
At this stage, the test team lead calculates the predicted time and cost for the test run. The scope of the test is decisive and appropriately the risks to be taken or not to be taken are evaluate. This phase starts after the requirement analysis phase is completed.
Test conditions are determined based on the analysis of required test resources and test items. Writing test scenarios and preparing the test environment takes place at this stage.
In Beyn Technology, at this stage, the necessary test resources are determined first. This resource can be, for example, a browser that needs to be installed on a computer, or it can be a mobile device. Then, when the test will start and when it will end is determined and the date ranges are reported to the project leader or team leader.
Test Case Creation
It is the stage where test scenarios are prioritized and developed. The development activity is started immediately after the planning is complete. Scenarios are written in detail by the testing team. After the scenarios are prepared, they are reviewed by the test team leader.
Test Case Execution
The test execution phase includes the tests performed on the system using manual or automatic test tools. This phase is the Basic Testing Process where the main work is done. The test execution phase is the phase where the code is successfully executed.
Test implementation has the following major task:
- Create test suites
- Execute tests with scenarios and repeat failed tests
- Log test results daily and compare expected results with actual results
Bug Logging
It simply means a method of finding bugs in the application which is under test. At this stage, all feedbacks are reviewed, and if there are reported errors, a test is performed by taking them into account. After making sure that these bugs are fixed, the following step is passed.
In Beyn Technology, bugs that come as clients feedback or reported by teams at this stage are reviewed. Task is created for these bugs.
These bugs are fixed by the developer and the product is tested. After making sure that the reported error has been fixed, the task is routed to the related state.
Bug Fix & Re-Verification
After the developer makes the necessary arrangements and changes on the product, he/she makes the final checks of the code and forwards it to the test team. At this stage, the tester retests the modified code to check if the bug is fixed.
At this stage, as Beyn, a report is prepared about the situation after all testing processes are completed. Supporting elements such as a screenshot showing the bug, a screen recording showing that the bugs been fixed, and a backend log are used.
In the prepared report, all test stages are written step by step using plain language and the test process is completed.
