Use faker unique method to make sure filepath is always different
What does this MR do?
To address test flakiness #323701 (closed). Having generate a random word with suffix .txt
there is still a chance this word is same as the previous one causing
Fabrication of QA::Resource::Repository::Commit using the API failed (400) with `{"message":"A file with this name already exists"}`.
Explicitly calling unique
to ensure uniqueness between back to back file commits.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
- [-] Separation of EE specific content
Related to #323701 (closed)