BDD talks about how a piece of code, application, or system should behave, and then capture these examples, often using the BDD tool and / or automation system. Many people only get value from capturing examples on the wiki. There are four things that I like in place before people move on to tools, especially if you are going to do this at the application level:
- Eye of the big picture
- Possibility of polling and studying
- Ability to determine uncertainty and determine uncertainty
- Great relationships between people.
, . , , Cucumber JBehave. G/W/T , , .
DSL , TestNG , NUnit , "//" . , . , , .
, :
, BDD . , , , .
. , . , Agile Testing, , , . , /API . , , . , , , , .
- , , / . . , , (: , ..)
, , , ; , . JBehave .
API , , , , .
. . 2 . , , , , , . : ", " ", ".
, , . TestNG . Page Object, , . , .
, DSL , , , , .