Java Testing - JUnit 5 Crash Course
video description
Date: 2022-03-14
Related videos
Comments and reviews: 8
Alexey
Great video, but I have a question. Why don't you validate the parameters in the setters and the constructor of Contact, but use separate validation methods for this purpose. Those methods may not be called at all, then the object will be in an incorrect state.
reply
Great video, but I have a question. Why don't you validate the parameters in the setters and the constructor of Contact, but use separate validation methods for this purpose. Those methods may not be called at all, then the object will be in an incorrect state.
reply
blasttrash
Spock(in groovy) is much better than JUnit. Data Tables are amazing feature and you will never go back to JUnit or Jest or any other language's framework. Write your code in java, kotlin etc, but write tests in groovy(spock).
reply
Spock(in groovy) is much better than JUnit. Data Tables are amazing feature and you will never go back to JUnit or Jest or any other language's framework. Write your code in java, kotlin etc, but write tests in groovy(spock).
reply
Lance
But well good showing all, but we need more first diagrams to understand the really concept, also why you don't use setup then before, I understand all but it need more abstraction also to for all understand all the concepts well.
reply
But well good showing all, but we need more first diagrams to understand the really concept, also why you don't use setup then before, I understand all but it need more abstraction also to for all understand all the concepts well.
reply
Ben
So far I really like your content and appreciate it! Maybe I'm alone on this one, but I'd find it more helpful if you slowed down the process a bit. Personally, it helps me follow your logic more clearly
reply
So far I really like your content and appreciate it! Maybe I'm alone on this one, but I'd find it more helpful if you slowed down the process a bit. Personally, it helps me follow your logic more clearly
reply
avff
We can delete -BeforeEach public void setup()-ContactManager = new ContactManager();- and do...
class ContactManagerTest-
private final ContactManager contactManager = new ContactManager();
-
reply
We can delete -BeforeEach public void setup()-ContactManager = new ContactManager();- and do...
class ContactManagerTest-
private final ContactManager contactManager = new ContactManager();
-
reply
Willi
Some say that there are some repos on GitHub that people collaborate for technical writing that pay. Any you know please recommend to me. With minimal needs to get started
reply
Some say that there are some repos on GitHub that people collaborate for technical writing that pay. Any you know please recommend to me. With minimal needs to get started
reply
Ioan
Skip the clatter with maven dependencies etc, and start with creating a new test class -05:49. Other than this is a very thorough explanation -
reply
Skip the clatter with maven dependencies etc, and start with creating a new test class -05:49. Other than this is a very thorough explanation -
reply
Chetan
Is JUnit5 really better than JUnit4 ?
Having a single jar is still better than having granular structure requiring ugly maven projects.
reply
Is JUnit5 really better than JUnit4 ?
Having a single jar is still better than having granular structure requiring ugly maven projects.
reply
Add a review, comment
Other channel videos
