Tasks and Duties
For this week's task, you are to familiarize yourself with a public-domain software of your choice and document its key functional and non-functional requirements. This will help you understand the software in detail, which is crucial for an effective manual QA. The software can be any open-source application or web-based system that is publicly available. Your deliverable will be a DOC file that clearly outlines the software's key features, user flow, and its functional & non-functional requirements. This document should be written in a clear and concise manner, and it should be easy to understand even for someone who is not familiar with the software. Evaluation will be based on the thoroughness of your understanding and the clarity of your documentation. The task is expected to take around 30-35 hours to complete.
This week, you are required to create detailed test cases for the software you chose in Week 1. The test cases should cover both positive and negative scenarios and should be designed to thoroughly test the software's functionality and performance. The test cases should be documented in a structured format in a DOC file with sections such as 'Test Case ID', 'Test Scenario', 'Test Steps', 'Expected Result', 'Actual Result', and 'Status'. You should also include a brief description of the purpose of each test case. Evaluation will be based on the completeness and clarity of the test cases and their coverage of the software's functionality and performance. The task is expected to take around 30-35 hours.
This week's task involves manually executing the test cases you developed in Week 2. You are expected to document the outcomes of each test case in the 'Actual Result' and 'Status' fields of your test case document. This task requires careful observation and precision to ensure that any deviations from the expected outcomes are accurately recorded. Your deliverable will be the updated DOC file with the test execution results. Evaluation will be based on the accuracy of your test execution and the thoroughness of your documentation. The task is expected to take around 30-35 hours.
In Week 4, you are required to report any bugs or issues found during the test execution in Week 3. You should document each bug in a separate section in your DOC file, with details such as 'Bug ID', 'Severity', 'Description of the Bug', 'Steps to Reproduce', 'Expected Result', 'Actual Result', and 'Screenshots (if any)'. Remember, a good bug report is one that is clear and detailed enough for a developer to understand and reproduce the issue. Evaluation will be based on the clarity and detail of your bug reports. The task is expected to take around 30-35 hours.
The final week's task is to prepare a comprehensive test report. This report should summarize the testing activities, including the number of test cases executed, the number of bugs found, the severity of each bug, and recommendations for improvement. You should also reflect on the testing process and provide insights into what worked well and what could be improved. The deliverable will be a DOC file with your detailed test report. Evaluation will be based on the completeness of the test report, the insights provided, and the clarity of the document. The task is expected to take around 30-35 hours.