Fix Integration tests#665
Merged
aatmanvaidya merged 4 commits intotattle-made:developmentfrom Aug 8, 2025
Merged
Conversation
Collaborator
|
@omkar-334 yes we will have to write separate integration tests for feluda and each operator. Let's keep that for another PR/issue |
aatmanvaidya
reviewed
Aug 7, 2025
aatmanvaidya
approved these changes
Aug 8, 2025
Closed
Closed
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
2 participants
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.
Resolves #663
@aatmanvaidya I had a doubt - Now that we have individual tests for each operator, do we need the integration tests for single operators?
Assuming these test the integration between feluda factory and the operator, this is already done in their own tests right?