You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are no unit tests for utility functions in the project. This is important to ensure that these functions work as expected and can be safely updated in the future. Adding tests will improve the reliability of the project and make it easier to spot issues early.
Steps to Reproduce:
Identify the utility functions in the project.
Write unit tests for each utility function using a testing framework like Jest.
Ensure the tests cover different edge cases and scenarios for each utility function.
Expected Outcome:
A set of unit tests for utility functions that ensures they perform as expected. These tests should be run automatically as part of the CI pipeline to catch any regressions.
Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊
You can also check our CONTRIBUTING.md for guidelines on contributing to this project.
harmeetsingh11
changed the title
[Tests]: Add Unit Tests for Utility Functions
[Testing]: Add Unit Tests for Utility Functions
Jan 19, 2025
Description
Currently, there are no unit tests for utility functions in the project. This is important to ensure that these functions work as expected and can be safely updated in the future. Adding tests will improve the reliability of the project and make it easier to spot issues early.
Steps to Reproduce:
Expected Outcome:
A set of unit tests for utility functions that ensures they perform as expected. These tests should be run automatically as part of the CI pipeline to catch any regressions.
Implementation Details (optional)
No response
Screenshots
No response
Checklist
The text was updated successfully, but these errors were encountered: