Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vbs-test-suite #166

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

ABHISHEKSONI121
Copy link
Collaborator

@ABHISHEKSONI121 ABHISHEKSONI121 commented Jul 24, 2024

Summary

VBS Test Suite Implementation

This pull request introduces a comprehensive test suite for our VBS scripts, significantly enhancing our codebase's reliability and maintainability. Here's a detailed breakdown of the changes and their benefits:

  1. Wrapper Classes:

    • Created Python wrapper classes for each VBS script
      Factura_Electronica_Wrapper.py pyi25_wrapper.py pyqr_wrapper.py Remito_Electronico_Carnico_Wrapper.py
    • These wrappers encapsulate VBS functionality in a Pythonic, object-oriented structure.
    • Enables easier integration with Python testing frameworks and modern development practices.
  2. Test Files:

    • Implemented separate test files for each VBS script.
    • Each test file contains multiple test cases covering various scenarios and edge cases.
  3. Test Coverage:

    • Achieved 100% test coverage for wrapper classes.
    • Leveraged pytest for its powerful testing capabilities and fixtures.
    • Utilized monkeypatch for mocking external dependencies, ensuring isolated unit tests.
    • Implemented tests for all key functionalities including authentication, connection, data creation, and API calls.
    • Added tests to verify proper error handling and edge cases.
    • The test suite is designed to run efficiently, with minimal setup and teardown overhead.
    • Added inline comments and docstrings to explain complex parts of the test suite.
  4. Performance:

    • The test suite is designed to run efficiently, with minimal setup and teardown overhead.

Checklist

  • Classes, Variables, function and methods logic ok
  • Comments written explaining what the code does
  • All python code is PEP8 compliant (run black .)
  • No lint issues (run flake8)
  • Test coverage with pytest implemented
  • Reviewers assigned (at least 1 mentor)

Signed-off-by: SONIABHISHEK121 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant