chore: add more tests to Formbricks Api Service#15
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
1 participant
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.
This pull request adds three new test cases to the
FormbricksApiServiceInstrumentedTestclass to improve the robustness and reliability of theFormbricksApiServiceby covering additional edge cases.New test cases added:
Error handling for null attributes in
postUser:testPostUser_withNullAttributes_handlesErrorGracefullyto ensure thepostUsermethod handles cases where user attributes arenullwithout crashing.Robustness of multiple initializations:
testInitialize_multipleTimes_noCrashto verify that callinginitializemultiple times with different configurations does not result in a crash or exception.Behavior before initialization:
testGetEnvironmentStateObject_beforeInitialize_returnsFailureto confirm that callinggetEnvironmentStateObjectbefore initializing the service fails gracefully with an appropriate exception (UninitializedPropertyAccessException).