Комментарии:
Brilliant series! Great way of teaching stuff in a memorable and professional way! Keep it up!
ОтветитьGreat video! Very clear definition of how BDD is and how it operates for those who are technical and non-technical.
ОтветитьNice video! Very straight forward and clear. Keep up with great work!
ОтветитьSo UITesting is basically Behavioral testing?
ОтветитьVery nice description of BDD
ОтветитьSo BDD is just TDD with less code coverage?
ОтветитьAwesome explanation.
ОтветитьExcellent video :)
ОтветитьExcellent explanation
Ответитьjust another mumbo jumbo word for something trivial
ОтветитьGreat explanation! Keep up the good work
ОтветитьAwesome video! Thanks a lot!
ОтветитьAwesome bro... And plz subscribe to my channel plz bro
ОтветитьVery nice video!... Please please keep it up..
ОтветитьSuperb explanation straight to the point
ОтветитьAwesome and simple way of teaching concepts, I appreciate it.
ОтветитьBDD has the winning CEO formula
Context
Event
Outcome
PETROL
ОтветитьIsn't BDD, in simple terms, the process of defining user requirements? So, this would include (in an agile setup) 3 amigos, refinements, client workshops, etc. The end result will be a complete user story which will then be a single source of truth for devs when actually implementing the code.
Or am I missing something?
Thx guy 👍🏻
ОтветитьThanks for this video, I now know what behavior driven development is
ОтветитьIs bdd of any value? JUnit test the code at the unit level. Integration test will test real data. What is BDD for ? for whom? Business Analysts don't care. Developers need Junit and integration test. BDD is for no one except for people who wants someone else to do it.
ОтветитьExplained in a very clear way, thanks.
ОтветитьI love and hate this description as it is both really good and really bad.
As the inventor of BDD - Dan North - said: "BDD is NOT about testing !"
Testing is only small part of what BDD is.
BDD is:
1. specifications for developer to implementing the feature
2. test plan & suite that can be used to automagically generate and enforce testing of the software behaviour
3. Living documentation (and changelog) of how the software you created works.
4. Comminication accross all the stakeholder of the project
etc.