MANUAL TEST

What the Manual Test is !

Manual testing is the process of using the functions and features of an application as an end-user would in order to verify the software is working as required.

How does Manual Test WORK!

1.     Requirement Analysis

First of all the tester needs to understand the requirements of the software or application that successfully conduct Manual Tests. By understanding the requirements, he’ll know what needs to be tested and what classifies a defect. It is an important part of manual testing as the main goal is to make sure the software is bug-free.

2.     Test Plan Creation

Once the tester understands the requirements, the tester can create test Plans – another part of Manual Test. Test plans guide the tester through a sequence of steps to test functions and different scenarios within the software application

• Entry Criteria
• Exit Criteria
• Dependency
• Test Phases

3.     Test Cases Creation

After creating the Test plan the tester is now ready to write Test cases which is important part of this Test. Test cases guide the tester through plan of sequence of steps to test functions and different scenarios within the software application. Writing good test cases is important as it makes executing the tests go smoothly and ensures good test coverage. Good test cases also allow future testers to go in and conduct the tests.

4.     Test Case Execution

Once the test cases are written and the testing environment is prepared, it’s time to begin testing. Monitor the test cases and mark each test as “passed”, “failed, or “No Results”. When doing manual testing, it’s important to keep notes on what happens when a test fails.

In addition to actually testing, the tester is responsible for logging bugs. As the Tester meets bugs, he needs to log information for the development team about the defect. Writing good bug reports help the team.

5.     Defects Loggings

At the core, a good bug report should have a strong title, steps to replicate the bug (often the test case steps), expected & actual result, and any relevant attachments that will help the development team understand the issue (screenshots, screen recordings, export files, etc.).

After running tests, it’s good to know the results of the tests at a high level. How many tests were ran? How many tests failed? How many tests had no results? How many tests were skipped? TestLodge makes it easy to get a quick glance of these metrics.

6.     Defect fix & Re-verify

After submitting the lodge, the developers will fix the defects and will consider to verify again the software or applications.

When And Why To Manual Test

Manual testing requires a lot of effort. It’s easy to just say “let’s skip it” or “let’s automate it”. But the truth is, it is imperative to building software because automated testing can’t cover everything. After all, humans will be using Tester software, therefore humans should be involved in testing Tester software. Manual testing is more likely to find and solve real usability issues than automated testing. It allows the tester to be flexible during the test and try different things on the fly.

This isn’t to say automated testing is useless. Automated testing has its own benefits and provides value in certain areas manual testing does not.

Conclusion

Manual testing is an activity where the tester needs to be very patient, creative & open minded. They need to think and act with an End User perspective.

 Although it requires a large amount of work, manual testing is necessary in order to ensure a good user experience and a high level of quality. A human tester is always going to find things an automated test won’t find. The keys to successful manual testing include understanding the requirements of the software, writing good test cases, and logging thorough bug reports.