Missing Automated Tests / CI Integration

[ishika24755]

Description

The RenAIssance repository currently lacks automated tests and a CI workflow.
As a result:

• Code changes may break functionality silently
• Contributors cannot verify that their changes work
• Regression bugs may go unnoticed

Proposed Solution

• Add unit tests for core modules (e.g., data preprocessing, model training, evaluation scripts)
• Configure GitHub Actions (or another CI system) to run the tests on every pull request
• Ensure tests run on multiple environments (e.g., Python 3.9, 3.10)

Why This Is Important

Adding tests and CI will:

• Improve code quality and reliability
• Reduce bugs for contributors
• Make the project more maintainable and trustworthy for users

[swagat-mishra28]

Hi @ishika24755,

I’ve submitted a pull request that introduces an initial automated testing setup along with a CI workflow for the repository.

The changes include:

• Adding a tests/ directory with basic unit tests for utility functions such as remove_punctuation and similarity_score, ensuring that core helper logic can be verified automatically.

• Introducing a GitHub Actions workflow (.github/workflows/tests.yml) that runs the test suite automatically on every push and pull request.

• Configuring the workflow to install project dependencies from RenAIssance_Transformer/requirements.txt and execute the tests using pytest.

• Running the CI pipeline across multiple Python versions (3.9 and 3.10) to improve compatibility.

This establishes a foundation for automated testing and CI in the repository and can be expanded with additional tests for other modules in the future.

PR: #81

[abhiram123467]

Hi, I notice the existing PRs (#61, #81) cover the Transformer module. I would like to contribute unit tests specifically for the CRNN OCR-1 module — covering ResNet18/34 classification head, CTC loss pipeline, and the LLM post-processing module (PR #104). I will submit a separate PR shortly.