Add unit tests for findUniqueFileName #6623
Open
+75
−7
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.
Description (required)
Fixes #5923
What changes did you make and why?
findUniqueFileNameinUploadWorker.ktto replace the old 5-digit random hash format(12345)with the requested 3-digit hash format#XXX.UploadWorkerTest.ktto ensure the filename generation logic is robust.findUniqueFileNamevisibility tointernalto allow unit test access while maintaining module-level encapsulation.Why?
The previous 5-digit format did not meeet the updated project requirements. these changes align the naming convention with the
#XXXstandard and provide automated testing to ensure filenames are generated correctly and remain unique.Tests performed (required)
Tested ProdDebug build variant on Local Unit Tests (JUnit 4).