🚨 Missing `pytest` Code for Testing the Package with Coverage Target of 90%+

[ARYAN-NIKNEZHAD]

Description:

The package currently lacks a comprehensive test suite, which is essential to ensure code reliability, maintainability, and the prevention of regressions. Specifically, there are no pytest test cases implemented, and the project does not meet the required test coverage of 90% or higher.

Having automated tests is critical for catching bugs early and maintaining high-quality software, especially as the codebase grows or new features are added.

Problems Identified:

1. No Test Coverage:

   • The absence of tests makes it difficult to verify whether the current functionalities are working as expected. This can lead to:
     • Bugs or regressions in the code going undetected.
     • Uncertainty during future refactors or updates.

2. Risk of Regressions:

   • Without proper tests in place, introducing new features or refactoring existing code can break existing functionality without being noticed.

3. No Confidence in Code Quality:

   • Missing tests reduce confidence in the codebase's stability. Teams or contributors may find it difficult to trust that changes made will not introduce issues.

4. No Continuous Integration of Testing:

   • Without tests, there's no integration of automated testing in the continuous integration (CI) pipeline to ensure changes are safe before merging them into the main branch.

5. No Code Coverage Target:

   • The package does not have a defined coverage goal, and with no tests, the coverage percentage is 0%. A coverage goal ensures that most of the code is covered by tests, reducing the chances of bugs in untested areas.