Manual Tester Life Cycle (MTLC)

The need to categorize each testing life cycle has become essential as a result of how much software testing is evolving. There are activitines as a manual tester that you take when working on a project. For me, the manual tester life cycle will be the same whether it is a waterfall or agile approach.

The following are the activities as a Manual Tester:

1. Requirement Analysis — you must first understand the specification for the software requirements. You will find this useful when making the test cases.
2. Understanding the Test Plan Approach — knowing the test plan’s testing methodology will help you understand how manual tests are carried out and how defect management is handled.
3. Test Cases Creation — creation of test cases is an important factor of manual testing activities. This will be used to document the project’s development. Make sure the test cases can be reused and that versioning is done properly.
4. Test Cases Execution — traceability for the implemented feature will be provided by test execution. Screenshots must to be provided for both passed and failed scenarios. However, failing scenarios should be the only thing you need to have a screenshot of if you’re using an Agile methodology.
5. Defect Logging — giving clear instructions on how the issue occurred will speed up the fixing process. I recommend you to use Chrome for some debugging, and it would be nice if you could provide some logs.
6. Re-Testing — when there are bugs or a need to retest the application, this is the last step.

The following are the instructions for carrying out the preceding steps:

• Activities 1 and 2 will usually be completed during the first stage of the testing procedure.
• Each testing cycle for your project will have activities 3 to 6. No matter if it’s every two weeks, every month, etc.