Комментарии:
checkIfContactAlreadyExist ???
ОтветитьI think validation in POJO class, is very BAD idea. What will you do if validation fails?
ОтветитьPerfect tutorial! Thank you very much <3
Ответитьhow to open github project files in itelliJ? I mean I able to open to open but can not run the code? Everytime I run the code pop up comes "Edit Configuration" .I don't know how to configure it. Please Help
ОтветитьThanks for your time on the video, dude!
ОтветитьHi how can we do parameterized tests for json files?
ОтветитьCan anyone here explain in layman's term what this lambda expression means? Thanks in advance.
This one: () ->
Excellent 🎉. Thanks
ОтветитьGreat content..
ОтветитьSai...is a rockstar !
ОтветитьYou don't have the test directory set up in your starter project and you already have one set up in the video without explaining how to. This is really confusing.
ОтветитьGreat tutorial. Just enough information and no fluff.
Ответитьgreat tutorial
ОтветитьBy default, the Lifecycle of a Test class is PER_METHOD, so, after each test method is executed, the constructor of the Test class is called. This can be changed by using the @TestInstance(TestInstance.Lifecycle.PER_CLASS). Mentioning as additional point Just in case.
Ответить@ProgrammingTechie Thank you, this really helped me understand how to write JUnit tests. Can you please tell me the name of the icon pack that you're using?
Ответитьu speak very fast , but ur explanation is too good
Ответитьway better tutorials out there
ОтветитьYou speak super fast and your English accent is bad. You go through what you "explain" too fast.
Ответитьright to the point! thanks
ОтветитьThanks for this mate
Ответитьthank you so much, you‘re a lifesaver!!
Ответитьcopy paste thats all you Indians can do , and shamelessly you call yourselves `Engineers` .......
Ответить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.
ОтветитьGreat explanation, thanks
Ответитьthankyou very much sir
ОтветитьWe can delete @BeforeEach public void setup(){ContactManager = new ContactManager();} and do...
class ContactManagerTest{
private final ContactManager contactManager = new ContactManager();
}
When you remove from pom version you have latest version jupiter :)
ОтветитьWhat software are you using?
ОтветитьUnfortunately, I can't dislike more than once
ОтветитьConcise and precise. A very good tutorial.
ОтветитьThese theme color is awesome. Can you say for its setting??
ОтветитьExcellent Work man.
ОтветитьPlease post katalon studio full tutorial
ОтветитьVery clean. Thanks!
ОтветитьThanks for this, I was having some problems using this because problems between 4 & 5.
ОтветитьThis is very good video ,Thank you !
ОтветитьIn the nested test of parameterized test, how does the static function providing the list doesn't throw an error?
ОтветитьThis tutorial helped alot ❤️
ОтветитьThis is a very good video. And I am realizing that 99% of my methods return void
ОтветитьThis is one of the best tutorials I've ever seen! Thank you!
ОтветитьExcellent Excellent to be infinite.
ОтветитьVery helpful. Thank you, sir.
Ответитьvery well done.
ОтветитьIs JUnit5 really better than JUnit4 ?
Having a single jar is still better than having granular structure requiring ugly maven projects.
Why does the AfterAll and BeforeAll have to have a static before the @TestInstance is implemented?
ОтветитьThank you for this !
Ответитьvery good video
Ответить