test: Add unit test for projects/app/src/pages/api/core/dataset/training/updateTrainingData.ts #5194
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.
Trigger Info
Summary
This PR introduces unit tests for the
updateTrainingData
API handler to ensure its functionality and reliability. Key changes include:Export Handler: The
handler
function is now exported fromupdateTrainingData.ts
for testing purposes.Unit Tests:
Retry All Error Data: Tests the scenario where
dataId
is not provided, ensuring all error data is retried.Update Single Training Data with Image: Validates the update logic when training data includes an image.
Update Single Training Data without Image: Ensures proper handling and update when training data does not include an image.
Reject When Data Not Found: Confirms the handler rejects the request when the specified data is not found.
Mocking Dependencies:
Mocked
MongoDatasetTraining
methods (findOne
,updateOne
,updateMany
) to simulate database interactions.Mocked
authDatasetCollection
to simulate authentication and authorization checks.These tests enhance the robustness of the
updateTrainingData
API by verifying its behavior under various conditions.Coverage
The change in coverage value, such as:
0% -> 50%
, indicates that the coverage was 0% before writing the tests and 50% after writing them.https://web.dev/articles/ta-code-coverage
Test Statuses
Tip
You can
@gru-agent
and leave your feedback. TestGru will make adjustments based on your inputTip
You can
@gru-agent rebase
to rebase the PR.Tip
You can
@gru-agent redo
to reset or rebase before redoing the PR.Tip
To modify the test code yourself, click here Edit Test Code