vaadin / vaadin/browserless-test
Detecting custom testers takes a lot of time
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 51
Description
Executing similar simple test with Karibu is thus ~ 50% faster.
Testable with https://github.com/mstahv/calc-ui-unit-testing :
- Import to IDE
- Execute test class separately: Karibu ~ 500ms, TestBench ~ 1200ms
Probably should either cache the lookup somehow or utilize e.g. Jandex indexing.
CC: @mcollovati @caalador, discussed on Friday.
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
No source file or test entry point is named. Reproduce the comparison using the calc-ui-unit-testing project by importing it into an IDE and executing the test class separately with Karibu and TestBench. Done means identifying and implementing a supported way to reduce custom-tester lookup time, then confirming the benchmark improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100