https://github.com/mrrajak1296/hackathon-orangehrm-code6343

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
https://github.com/mrrajak1296/hackathon-orangehrm-code6343

cucumber-java page-object-model selenium

Last synced: about 2 months ago
JSON representation

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

• Host: GitHub
• URL: https://github.com/mrrajak1296/hackathon-orangehrm-code6343
• Owner: mrrajak1296
• Created: 2025-01-17T07:46:25.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2025-01-25T10:26:10.000Z (over 1 year ago)
• Last Synced: 2025-01-25T11:19:47.084Z (over 1 year ago)
• Topics: cucumber-java, page-object-model, selenium
• Language: Java
• Homepage: https://opensource-demo.orangehrmlive.com/web/index.php/auth/login
• Size: 85.9 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# Hackathon-Code6343

# Link - https://opensource-demo.orangehrmlive.com/web/index.php/auth/login

# 1 .Introduction:-

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.

# 2.Test Objective:-

●	State the goals of the testing process (e.g., validate functionality, performance, Usability).

●	Specify the expected outcomes.

# 3.Testing Scope:-

       The scope of this test plan includes:

1.	Authentication (Login/Logout).

2.	Navigation through the dashboard and various modules.

3.	Employee Management functionalities.

4.	Leave Management workflows.

5.	Recruitment processes.

6.	Performance evaluation module.

7.	UI/UX and browser compatibility testing.

8.	Security testing (basic checks).

9.	Performance testing.

# 4. Test Schedule Duration:

 ● TestPlanning Phase: 48 Hours

# 5. Test Coverage: -

The test coverage will include functional, non-functional, and security, performance & compatibility testing across the features to be tested.

 Functional Testing:

 1. Login/Registration: Test user sign-up, login, and profile updates. 

2. MenuDisplay and Search: Ensure menus display correctly and searches return accurate results. 

3.OrderPlacement: Verify that users can add items, update quantities, and place orders. 

4. OrderTracking: Ensure users can track their order status. 

5. Ratings and Reviews: Test the functionality of submitting and viewing ratings and reviews. 

# Non-functional Testing: 

1. Performance Testing: Verify the app's performance under normal and peak loads (e.g., load time, transaction time). 

2. Usability Testing: Ensure that the app is user-friendly, with an intuitive interface.

# 6.Test Approach:-

1. 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

# 7.Roles and Responsibilities:-

# 1. Anil Rajak (Test Lead)

•	Role: Test Lead (Automation Testing Specialist)

•	Responsibilities:

o	Plan and oversee the testing process, ensuring quality and deadlines are met.

o	Create and manage test strategies, plans, and schedules.

o	Develop, execute, and maintain automation test scripts for critical workflows.

o	Coordinate between the testing team and stakeholders for status updates and issue resolution.

o	Review automation test cases created by the team for completeness and accuracy.

o	Identify risks and provide mitigation strategies for the testing process.

o	Ensure adherence to best practices in automation testing.

# 2. Sonu Singh (Automation Tester)

•	Role: Automation Tester

•	Responsibilities:

o	Design, develop, and execute automation scripts for various modules (e.g., Employee Management, Leave Management).

o	Collaborate with the Test Lead to identify areas for automation and optimize testing workflows.

o	Debug and resolve issues in test scripts to ensure stability.

o	Validate test results, log defects, and track them to closure.

o	Maintain documentation for test automation frameworks and processes.

# 3. Balaji Chavan (Manual Tester)

•	Role: Manual Tester

•	Responsibilities:

o	Execute manual test cases for functional, usability, and UI testing.

o	Identify and log defects with detailed reproduction steps in the defect tracking tool.

o	Perform exploratory testing to uncover edge cases and usability issues.

o	Validate fixes for reported defects and perform regression testing.

o	Document test cases, test scenarios, and test results comprehensively.

o	Ensure application meets quality standards and aligns with user requirements.

# 8. Deliverables:

 1. TestPlan Document: A detailed plan outlining the testing scope, strategy, and schedule. 

2. TestCases: Specific scenarios to be tested, detailing the input, expected results, and testing steps. 

3. TestExecution Report: Status updates during the test execution phase, including passed/failed test cases and defect logs. 

4. Defect Logs: A detailed record of defects identified, their severity, and resolution status.  

5.Final Test Report: A comprehensive report summarizing all testing activities, issues found, and the status of testing.

 6. TestClosure Report: Documentation of lessons learned, final sign-offs, and recommendations for future testing

# 9. Entry and Exit Criteria

Entry Criteria:

●	Requirements are finalized.

●	Test Planning is ready.

●	Test data is prepared.

Exit Criteria:

●	All planned test cases are executed.

●	Critical defects are resolved.

●	Test summary report is completed.

# 10. Risks and Mitigations

●	Identify potential risks (e.g., delays, resource issues).

●	Provide mitigation strategies for each risk.

# 11. Approvals Required:

 1 TestPlan Approval: From the project manager and other stakeholders (e.g., business analysts, product managers). 

2. TestCases Approval: From the development team to ensure that test cases cover all requirements. 

3. TestExecution:- After each testing cycle (e.g., functional and performance testing), a sign-off from stakeholders confirming the test results. 

4. 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