vaadin / vaadin/browserless-test
The "verbs" in "Testers" API should be more like user actions than Component API replicas
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 51
Description
The "verbs" in "Testers" API should be more like user actions than replicas made of Component API.
e.g. setValue(String) -> fill(String)
Arguments:
- Test cases would be more like a usage descriptions (especially together with #38)
- It wouldn't be that easy to accidentally mix wheter one is using the actual components or simulating user actions on it
- API would be more like in Playwright, which is more familiar with general audience
Contributor guide
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
Start by reviewing the Testers API and comparing its verbs with the Component API, using setValue(String) -> fill(String) as the concrete example. Define the user-action vocabulary consistently, while checking the relationship with issue #38. Done means the Testers API uses distinct, user-oriented verbs rather than Component API replicas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100