{"id":24649033,"url":"https://github.com/mrrajak1296/hackathon-orangehrm-code6343","last_synced_at":"2026-04-10T16:52:41.194Z","repository":{"id":273208377,"uuid":"918074358","full_name":"mrrajak1296/Hackathon-OrangeHRM-Code6343","owner":"mrrajak1296","description":"The OrangeHRM  website serves as a platform for users to explore and evaluate the features of the OrangeHRM software, an open-source Human Resource Management (HRM) solution. It is designed to streamline HR processes and provides tools for managing employee data, leave requests, time tracking, recruitment, and performance evaluations ","archived":false,"fork":false,"pushed_at":"2025-01-25T10:26:10.000Z","size":88,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-01-25T11:19:47.084Z","etag":null,"topics":["cucumber-java","page-object-model","selenium"],"latest_commit_sha":null,"homepage":"https://opensource-demo.orangehrmlive.com/web/index.php/auth/login","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/mrrajak1296.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-01-17T07:46:25.000Z","updated_at":"2025-01-25T10:26:13.000Z","dependencies_parsed_at":"2025-01-25T11:19:50.568Z","dependency_job_id":null,"html_url":"https://github.com/mrrajak1296/Hackathon-OrangeHRM-Code6343","commit_stats":null,"previous_names":["mrrajak1296/hackathon-code6343","mrrajak1296/hackathon-orangehrm-code6343"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrrajak1296%2FHackathon-OrangeHRM-Code6343","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrrajak1296%2FHackathon-OrangeHRM-Code6343/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrrajak1296%2FHackathon-OrangeHRM-Code6343/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrrajak1296%2FHackathon-OrangeHRM-Code6343/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mrrajak1296","download_url":"https://codeload.github.com/mrrajak1296/Hackathon-OrangeHRM-Code6343/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":244675507,"owners_count":20491824,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cucumber-java","page-object-model","selenium"],"created_at":"2025-01-25T17:15:25.528Z","updated_at":"2026-04-10T16:52:41.148Z","avatar_url":"https://github.com/mrrajak1296.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Hackathon-Code6343\n# Link - https://opensource-demo.orangehrmlive.com/web/index.php/auth/login\n\n# 1 .Introduction:-\nThe OrangeHRM  website serves as a platform for users to explore and evaluate the features of the OrangeHRM software, an open-source Human Resource Management (HRM) solution. It is designed to streamline HR processes and provides tools for managing employee data, leave requests, time tracking, recruitment, and performance evaluations.\n\n\n# 2.Test Objective:-\n●\tState the goals of the testing process (e.g., validate functionality, performance, Usability).\n●\tSpecify the expected outcomes.\n# 3.Testing Scope:-\n       The scope of this test plan includes:\n1.\tAuthentication (Login/Logout).\n2.\tNavigation through the dashboard and various modules.\n3.\tEmployee Management functionalities.\n4.\tLeave Management workflows.\n5.\tRecruitment processes.\n6.\tPerformance evaluation module.\n7.\tUI/UX and browser compatibility testing.\n8.\tSecurity testing (basic checks).\n9.\tPerformance testing.\n# 4. Test Schedule Duration:\n ● TestPlanning Phase: 48 Hours\n\n# 5. Test Coverage: -\nThe test coverage will include functional, non-functional, and security, performance \u0026 compatibility testing across the features to be tested.\n Functional Testing:\n 1. Login/Registration: Test user sign-up, login, and profile updates. \n2. MenuDisplay and Search: Ensure menus display correctly and searches return accurate results. \n3.OrderPlacement: Verify that users can add items, update quantities, and place orders. \n4. OrderTracking: Ensure users can track their order status. \n5. Ratings and Reviews: Test the functionality of submitting and viewing ratings and reviews. \n\n# Non-functional Testing: \n1. Performance Testing: Verify the app's performance under normal and peak loads (e.g., load time, transaction time). \n2. Usability Testing: Ensure that the app is user-friendly, with an intuitive interface.\n\n# 6.Test Approach:-\n1. Manual Testing:  Most features will be tested manually (user login, menu display, order placement, etc.), as these require human judgment, especially for UI/UX and functional testing\n\n# 7.Roles and Responsibilities:-\n# 1. Anil Rajak (Test Lead)\n•\tRole: Test Lead (Automation Testing Specialist)\n•\tResponsibilities:\no\tPlan and oversee the testing process, ensuring quality and deadlines are met.\no\tCreate and manage test strategies, plans, and schedules.\no\tDevelop, execute, and maintain automation test scripts for critical workflows.\no\tCoordinate between the testing team and stakeholders for status updates and issue resolution.\no\tReview automation test cases created by the team for completeness and accuracy.\no\tIdentify risks and provide mitigation strategies for the testing process.\no\tEnsure adherence to best practices in automation testing.\n# 2. Sonu Singh (Automation Tester)\n•\tRole: Automation Tester\n•\tResponsibilities:\no\tDesign, develop, and execute automation scripts for various modules (e.g., Employee Management, Leave Management).\no\tCollaborate with the Test Lead to identify areas for automation and optimize testing workflows.\no\tDebug and resolve issues in test scripts to ensure stability.\no\tValidate test results, log defects, and track them to closure.\no\tMaintain documentation for test automation frameworks and processes.\n# 3. Balaji Chavan (Manual Tester)\n•\tRole: Manual Tester\n•\tResponsibilities:\no\tExecute manual test cases for functional, usability, and UI testing.\no\tIdentify and log defects with detailed reproduction steps in the defect tracking tool.\no\tPerform exploratory testing to uncover edge cases and usability issues.\no\tValidate fixes for reported defects and perform regression testing.\no\tDocument test cases, test scenarios, and test results comprehensively.\no\tEnsure application meets quality standards and aligns with user requirements.\n\n\n# 8. Deliverables:\n 1. TestPlan Document: A detailed plan outlining the testing scope, strategy, and schedule. \n2. TestCases: Specific scenarios to be tested, detailing the input, expected results, and testing steps. \n3. TestExecution Report: Status updates during the test execution phase, including passed/failed test cases and defect logs. \n4. Defect Logs: A detailed record of defects identified, their severity, and resolution status.  \n5.Final Test Report: A comprehensive report summarizing all testing activities, issues found, and the status of testing.\n 6. TestClosure Report: Documentation of lessons learned, final sign-offs, and recommendations for future testing\n\n# 9. Entry and Exit Criteria\nEntry Criteria:\n●\tRequirements are finalized.\n●\tTest Planning is ready.\n●\tTest data is prepared.\n\nExit Criteria:\n●\tAll planned test cases are executed.\n●\tCritical defects are resolved.\n●\tTest summary report is completed.\n\n# 10. Risks and Mitigations\n●\tIdentify potential risks (e.g., delays, resource issues).\n●\tProvide mitigation strategies for each risk.\n# 11. Approvals Required:\n 1 TestPlan Approval: From the project manager and other stakeholders (e.g., business analysts, product managers). \n2. TestCases Approval: From the development team to ensure that test cases cover all requirements. \n3. TestExecution:- After each testing cycle (e.g., functional and performance testing), a sign-off from stakeholders confirming the test results. \n4. TestClosure Report Approval: A final sign-off from stakeholders once the testing is complete, ensuring that all critical features have been tested and any major defects have been resolved\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmrrajak1296%2Fhackathon-orangehrm-code6343","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmrrajak1296%2Fhackathon-orangehrm-code6343","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmrrajak1296%2Fhackathon-orangehrm-code6343/lists"}