test: 🥳 getRandomInRange can return same value as min value

[okinawaa]

I have verified that the value returned by getRandomInRange may be equal to the min value

I tried to modify getRandomInRange to return a value greater than the min value always, but I did not modify the function because the developer might think that the return value also contains a min value(can be equal).

Which do you prefer, fixing the test code or modifying the function?

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/falso/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

test code always pass all test

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[NetanelBasal]

Getting min is valid