Refactor asserts part 2

[vikassaini77]

Before submitting

• Self-reviewed the code
• Updated documentation, follow Google-style
• Added docs entry for autogeneration (if new functions/classes)
• Added/updated tests
• All tests pass locally

Description

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🧪 Test update
• 🔨 Refactoring (no functional changes)
• ⚡ Performance improvement
• 🔧 Chore (dependencies, configs, etc.)

Motivation and Context

Closes #(issue)

Changes Made

Testing

• I have tested this code locally
• I have added unit tests that prove my fix is effective or that my feature works
• All new and existing tests pass

Google Colab (optional)

Colab link:

Screenshots/Videos (optional)

Additional Notes

[CLAassistant]

All committers have signed the CLA.

[Borda]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@vikassaini77 pls sign. All your PRs have missed this, and without that we simply cannot merge it regardless of the quality and impact... 🦝

[Borda]

@vikassaini77 pls follow the contribution guidelines. In particular, it means you shall write PR description why it does and how it fixes or improves this package, then you have to sign the CLA (or provide a screenshot of what you did), otherwise, we cannot move forward, even I see based on your changes a value in your contribution 🦝