MarketSquare / MarketSquare/robotframework-faker
Care should be taken when adding new functions
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 69
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
We must not forget that the FakerLibrary is used by a group of users in productive test cases or tasks.
To ensure that users are not surprised by new functions, we should think very carefully about what we renew and how we guarantee that existing scripts are not affected.
One idea might be not to redevelop all the functions, but to implement providers, for example, that are responsible for generating the data in the Python Faker library.
> The ticket is the result of a discussion at the RBCN25 Community Day.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing FakerLibrary functions and the Python Faker provider approach, then define how compatibility with productive test cases and existing scripts will be checked. Done means an agreed approach for adding functions without affecting existing scripts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100