Develop comprehensive testing plan #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add comprehensive test suite and documentation to improve the reliability and maintainability of the Project-X Python financial trading API library.
This PR introduces a robust testing framework using pytest, covering core components and order management functionalities. It includes new test files for authentication, basic API operations, order manager initialization, order creation, modification, cancellation, and order status tracking. Several issues were identified and fixed during testing, including lazy authentication patterns, Polars DataFrame timestamp formatting, incorrect model imports (using integers instead of enums), and Order Manager attribute access. A detailed
TESTING_PLAN.mdandTEST_REPORT.mdare also included, outlining the current test coverage and known issues (e.g., SignalR mocking).