-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Substitute mockito with mockk and assertj with kluent #177
Conversation
ursjoss
commented
May 2, 2020
•
edited
Loading
edited
- Convert remaining tests to kotlin
- public-web
- core-web
- Remove dependencies:
- mockito
- mockito-kotlin
- assertj
- Manage performance - check effect of
- build scans from master and this branch to compare
- clearing mocks
- favour directly instantiating in code over annotations
314ddbf
to
eaea5e0
Compare
switching to my probably naive approach of substituting mockito with mock and assertj with kluent resulted in a build time for |
60b96ce
to
e98f02d
Compare
After implementing the clearing of all mocks, the total build time went even further up, from roughly 120 minutes to ~230 minutes :-( |
4dd2430
to
dae436c
Compare
* unmockAll() * dont mock relaxedly
* Avoid using mocks where possible * unmockAll * tester.destroy * Use AjaxTargetRequestSpy instead of mocking AjaxTargetRequest
Use LinkedHashSet instead of LinkedList to store the instances of IListener. This improves the time complexity in method addListener for the contains method from O(n) to O(1). This brings down the time spent for running the `gradlew check` command for the entire project from several hours to 20 minutes again (with mockk - mockito was not affected that much).
…ntaining insertion order" This reverts commit 2258b71.
This reverts commit 38840f6.
This reverts commit b878079.
1a7205b
to
0de4cd6
Compare
The wicket |
PR in wicket: apache/wicket#438 |