chore: add test for observation error level through langchain integration #637
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.
Important
Add test to verify observation level is set to ERROR when LangChain operation fails due to an invalid model name.
should set observation level to ERROR when LangChain operation fails
inlangchain.e3e.test.ts
.This description was created by
for 4f33777. You can customize this summary. It will automatically update as commits are pushed.
Disclaimer: Experimental PR review
Greptile Summary
Updated On: 2025-09-18 13:08:28 UTC
This PR adds a comprehensive test case to the LangChain end-to-end test suite to verify that the Langfuse CallbackHandler properly handles error scenarios. The test specifically validates that when a LangChain operation fails (such as using an invalid OpenAI model), the resulting Langfuse observation is correctly marked with
level='ERROR'
and includes the error details in thestatusMessage
field.The test follows the established pattern in the codebase by:
'invalid-model-name-that-does-not-exist'
This change enhances test coverage for the LangChain integration's error handling capabilities, ensuring that failed operations are properly tracked and observable in Langfuse traces for debugging and monitoring purposes. The test integrates seamlessly with the existing test infrastructure and follows the same timeout patterns (30 seconds) as other tests in the suite.
Confidence score: 5/5