QA TESTER PROJECT

You should work on Virtual Machine, the credentials for which were already shared with you on the Candidate’s Portal via Manage VMs menu. Use Windows Remote Desktop Connection to connect to the Virtual Machine computer as available from Manage VMs menu. You may use Internet Explorer Version 9 or higher for assignment to work. You may use MS Word \ MS Excel for Test Scenarios and Test Cases documentation. You may use Wink for the demo of found defects or odd behaviors to report. The Assignment: Software requirements: The OrangeHRM application is installed already in the VM that is deployed for you as in the instruction above. User Name - AdminOH Password - adminoh Objective: - Part 1 - Create all the functional End to End flow test cases for the following scenarios in OrangeHRM: A. For each of the following scenarios, Create a new employee profile, it's log-In credentials and validate that employee can login to the newly created OrangeHRM employee account. 1. Create Credentials at the time of employee creation. 2. Create Credentials after the completion of employee creation. B. In the PIM module of HRM application (available after login), Create a custom field for the additional information about an employee, it's usage and related verification. Note - Prepare the test data and include it wherever required in the test cases. You may keep test data separately. You are free to apply all the Test Case design techniques and the Testing types. Deliverable from this part: - A MS Word \ MS Excel doc\sheet named Scenarios_And_Test_Cases containing your Test Scenarios and Test Cases Part 2 - Write the GUI test cases for the GUI related to the specified scenarios as in the part 1: Note: - This is the space given for your diverse thinking for designing the test cases to find out pitfalls of the application if any. Deliverable from this part: - A MS Word \ MS Excel doc\sheet named Scenarios_And_Test_Cases_GUI containing your Test Scenarios and Test Cases. Part 3 - Execute the test cases designed from Part 1 and Part 2: Important instruction - keep test evidence to be submitted as a part of delivery. Note: In this part, you have to note down (for the below cumulative task) all the defects, odd behaviors found during the execution of your test cases. Deliverable from this part: - A MS Word \ MS Excel doc\sheet named Test_Execution_Evidence containing the evidence of the test execution including test steps and snapshots. Part 1, 2 and 3 - Cumulative task From all the parts in this assignment, you have to report all the defects, odd behaviors found during writing of test cases \ exploring the application and the execution of your test cases (i.e. noted in Part 3). Appropriately describe your defects, odd behaviors in Defects_Behaviors doc. Create a wink video recording that will show steps to reproduce each of them you've found. Deliverable from this part: - A document containing the defects, odd behaviors and their details, named [login to view URL] / .docx To be evaluated: The quality of your output (work) Completeness in each part of the assignment The documentation Delivery / What to submit Please, read and follow this section carefully. Any solution delivery that does not follow this section will score much less or simply won't be evaluated. Follow the Solution Delivery Instructions described as follows which should consist of: Archive named <Your_Name – Software Tester>.zip containing the following: ReadMe text file containing the summary of your work done and your feedback about the assignment. Scenarios_And_Test_Cases MS Word/Excel file Scenarios_And_Test_Cases_GUI MS Word/Excel file Test_Execution_Evidence MS Word/Excel file Defects_Behaviors MS Word file Wink Folder containing video recording of all defects or\and odd behaviors.