Mockito
AssertJ
Our great sponsors
Mockito | AssertJ | |
---|---|---|
11 | 14 | |
14,584 | 2,537 | |
0.9% | 0.9% | |
9.0 | 9.5 | |
5 days ago | 4 days ago | |
Java | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Mockito
-
Wednesday Links - Edition 2023-01-18
Mockito 5 Released (1 min)๐ https://github.com/mockito/mockito/releases/tag/v5.0.0
- Mockito 5.0.0 released, requires Java 11
- Mockito 5: prepare for future JDK versions
- 5 easy paths to become a recognized Java expert. Really. For free.
-
Mockito and non-debuggable testBuildTypes
For those using a "release" testBuildType for integration tests, what does your mocking setup look like? My app is stuck on Mockito 2.23.4, because higher (> 1.8.12) versions of Byte Buddy required beyond that point [do not play nicely with non-debuggable APKs](https://github.com/mockito/mockito/issues/2302). Solutions I've considered so far:
- Mockito - Most popular Mocking framework for unit tests written in Java
-
20+ Trending and Popular Java Open Source Project
Mockito
-
Reverse engineering Mockito. Part 2. Dynamic dependency injection
The code is pretty self explanatory but here's a quick run down. o.getClass().getDeclaredFields() gets us an array of all the fields. We then have a enhanced for loop that loops over the array. Check if the field is annotated field.isAnnotationPresent(Gucci.class). If it is then we set its modifier to true with field.setAccessible(true);. If we don't do this and the field is private we will get an error. Then we get the binary name of the field, field.getGenericType().getTypeName();, remember its just the package and the class name. Lastly we set the value of the field, field.set(o,dynamicInjection(classLoader,binaryName). With that we have now created a dependency injection annotation with the Junit 5 extension model. Now I am sure you can see the tower of exceptions, which is obviously not ideal. I'm not sure how I want to handle all the exceptions yet. However, I will be digging around the Mockito code base to see if I can find how they handle all their exceptions.
-
JVM Testing Newsletter | June 2021
Mockito 3.11.* releases
-
Writing Apache Parquet Files
Hi, I've been trying to write parquet files on android for the past couple of days, and have really been struggling to find a solution. My original hypothesis was to just use the java parquet implementation (https://github.com/apache/parquet-mr), but I've since realized that not all java libraries play well with Android. I've gone through essentially dependency hell trying to franken-fit the library into my project, and imported as much as i could before hitting walls such as this one (https://github.com/mockito/mockito/issues/841).
AssertJ
-
Announcing lets_expect - Clean tests in Rust.
Maybe not the feedback you want, but would you consider developing something that looks like plain old (and frankly beautiful) AssertJ?
-
7 Awesome Libraries for Java Unit & Integration Testing
AssertJ - fluent assertions
-
Any suggestions for good open source Java codebases to study(With below criteria)?
AssertJ https://github.com/assertj/assertj
- AssertJ: A fluent assertions Java library
-
Any resources for Unit Tests?
Truth or AssertJ for easier assertions in tests with better exceptions
-
Getting back into Java after 12-15 years away?
While we are at it: AssertJ is very powerful for writing assertions.
-
Imperative vs Declarative Programming
In OO you can make beautiful DSLs that allow really declarative use within that domain, e.g. test assertions in AssertJ, but everybody in the OO world is sensible enough to not try and claim OO as such being declarative. I guess they don't feel a need to try to prove the superiority of the paradigm.
-
Make your tests more readable using AssertJ and BDD syntax
AssertJ comes with a variety of assertions that can be chained together and are specific to the type of your "actual" variable.
-
How can I get rid of this warning? It's a warning for an "unchecked invocation".
At any rate it comes from a library called assertj.
-
Who here are using the Hamcrest API and why?
While Hamcrest add some fluentidity to unit tests รค, I prefer the fluent assertions of AssertJ.
What are some alternatives?
WireMock - A tool for mocking HTTP services
TestNG - TestNG testing framework
REST Assured - Java DSL for easy testing of REST services
Truth - Fluent assertions for Java and Android
MockServer - MockServer enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding).
Hamcrest - Java (and original) version of Hamcrest
Testcontainers - Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
Spock - The Enterprise-ready testing and specification framework.
Cucumber - Cucumber for the JVM
Selenium
junit5 - โ The 5th major version of the programmer-friendly testing framework for Java and the JVM