Gil Zilberfeld

46 Followers
48 Following
56 Posts
Most people think that 2+3=5.
Think? They know that. So much, that if they had code that does it, they wouldn't bother with a test.
But that's because they know how the code is written. If they didn't, would they still not bother?
Check it out.
https://www.everydayunittesting.com/2022/08/black-and-white.html #software
Black and White | Everyday Unit Testing

Black box, white box. Does our choice of perspective matter? We've landed this function declaration: public int add(int a, int b); We're told that it adds two integer numbers. How should we test it? Let's see, we can check that sending 2 and 3 returns 5. We can also send 3 and 4, and expect

Everyday Unit Testing | By Gil Zilberfeld
Mockito 5 Supports Mocking Constructors, Static Methods and Final Classes Out of the Box - https://www.infoq.com/news/2023/01/mockito-5/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
Mockito 5 Supports Mocking Constructors, Static Methods and Final Classes Out of the Box

Mockito has released version 5, switching the default mockmaker to mockito-inline in order to better support future versions of the JDK and allows mocking of constructors, static methods and final classes out of the box. The baseline increased from Java 8 to Java 11, as supporting both versions became costly and managing changes in the JDK such as with the SecurityManager proved difficult.

InfoQ
Gil’s Agile testing news

Testing, craftsmanship, agile and lean for better software by Gil Zilberfeld

paper.li
Gil’s Agile testing news

Testing, craftsmanship, agile and lean for better software by Gil Zilberfeld

paper.li
Welcome! You are invited to join a webinar: Microservices - Refactoring APIs to Patterns. After registering, you will receive a confirmation email about joining the webinar.

"Microservices allow for quick development and delivery. But if the code is, let's say, of the legacy persuasion, the development quickly slows down. Refactoring to rescue. And this time, it's not just about well-factored, readable code (although we really like it). We'll use common architectural and design patterns that make the code modular, extensible and testable. In this webinar, I'll take some (very ugly) microservice API code and refactor it. We'll make sure the domain logic is separated from the infrastructure code, and that the domain logic is unit testable. We'll discuss and use common design patterns (factories, repositories, etc.), and explain how using them helps keep the architecture flexible and maintainable. Once the code is factored, we'll see what additional tests we can write - and where they help us. Microservices code should be modular, cohesive and testable. If it's not - refactoring according to architecture and design patterns is the best way to get there."

Zoom
Welcome! You are invited to join a webinar: Microservices - Refactoring APIs to Patterns. After registering, you will receive a confirmation email about joining the webinar.

"Microservices allow for quick development and delivery. But if the code is, let's say, of the legacy persuasion, the development quickly slows down. Refactoring to rescue. And this time, it's not just about well-factored, readable code (although we really like it). We'll use common architectural and design patterns that make the code modular, extensible and testable. In this webinar, I'll take some (very ugly) microservice API code and refactor it. We'll make sure the domain logic is separated from the infrastructure code, and that the domain logic is unit testable. We'll discuss and use common design patterns (factories, repositories, etc.), and explain how using them helps keep the architecture flexible and maintainable. Once the code is factored, we'll see what additional tests we can write - and where they help us. Microservices code should be modular, cohesive and testable. If it's not - refactoring according to architecture and design patterns is the best way to get there."

Zoom
Gil’s Agile testing news

Testing, craftsmanship, agile and lean for better software by Gil Zilberfeld

paper.li

Webinar tomorrow!

"Microservices: Refactoring to patterns". With very big code and very small pasta.

Register here:
https://us02web.zoom.us/webinar/register/3816527847113/WN_sQffXtz9QremPmJ_zveAAA

Please RT!

Welcome! You are invited to join a webinar: Microservices - Refactoring APIs to Patterns. After registering, you will receive a confirmation email about joining the webinar.

"Microservices allow for quick development and delivery. But if the code is, let's say, of the legacy persuasion, the development quickly slows down. Refactoring to rescue. And this time, it's not just about well-factored, readable code (although we really like it). We'll use common architectural and design patterns that make the code modular, extensible and testable. In this webinar, I'll take some (very ugly) microservice API code and refactor it. We'll make sure the domain logic is separated from the infrastructure code, and that the domain logic is unit testable. We'll discuss and use common design patterns (factories, repositories, etc.), and explain how using them helps keep the architecture flexible and maintainable. Once the code is factored, we'll see what additional tests we can write - and where they help us. Microservices code should be modular, cohesive and testable. If it's not - refactoring according to architecture and design patterns is the best way to get there."

Zoom
What makes microservices testable? Glad you asked. I got a webinar for it. In two days.
Register her:
https://us02web.zoom.us/webinar/register/3816527847113/WN_sQffXtz9QremPmJ_zveAAA
Welcome! You are invited to join a webinar: Microservices - Refactoring APIs to Patterns. After registering, you will receive a confirmation email about joining the webinar.

"Microservices allow for quick development and delivery. But if the code is, let's say, of the legacy persuasion, the development quickly slows down. Refactoring to rescue. And this time, it's not just about well-factored, readable code (although we really like it). We'll use common architectural and design patterns that make the code modular, extensible and testable. In this webinar, I'll take some (very ugly) microservice API code and refactor it. We'll make sure the domain logic is separated from the infrastructure code, and that the domain logic is unit testable. We'll discuss and use common design patterns (factories, repositories, etc.), and explain how using them helps keep the architecture flexible and maintainable. Once the code is factored, we'll see what additional tests we can write - and where they help us. Microservices code should be modular, cohesive and testable. If it's not - refactoring according to architecture and design patterns is the best way to get there."

Zoom
Gil’s Agile testing news

Testing, craftsmanship, agile and lean for better software by Gil Zilberfeld

paper.li