- Phillip Thomas Isenborg Andersen, [email protected]
- Sumit Dey, [email protected]
- She did not hit him
- The gun was not powerful enough to kill him
- He might already have been dead
- The man is immortal so he can not be killed (Hit and arm, leg etc)
- He had a bullet-proof vest on
- He was standing at a range where he was too far away to die from the impact
- The gun did not function properly
- She was shooting at the mans reflection in the mirror
Step 1: First grab the toothpaste from the holder
Step 2: Screw of the cap counter-clockwise til the cap comes off completely
Step 3: Next up figure out which hand is your preferable to brush with
Step 4: With your preferable hand grab the toothbrush from the holder by the shaft so that the bristles are pointing upwards
Step 5: Squeeze some paste on to the bristles of the toothbrush and should be the size of your little finger
Step 6: Open your mouth and gently stick the toothbrush until it hits the your morals on either the right or left side
Step 7: Brush each tooth in small circular movement until they feel smooth
Step 8: Feel free to spit out the toothpaste so you don't swallow it.
Step 9: When all your teeth are smooth take the toothbrush out of your mouth
Step 10: Rinse your mouth with water and spit out any toothpaste residue left in your mouth
Step 11: Rinse the toothbrush bristles thoroughly and place in back in the holder
⚠️ Look in the source code folder
Use BDD to create a fahrenheit-to-celcius converter. Use BDD to extend it to a celcius-to-fahrenheit converter.
Implement an “Arabic numeral to roman numeral” converter using BDD
As a developer it gave me high visibility in terms of user requirements, since you start out by specifying a behavior, which is written in a simple neutral language. This is great if I was for example working in close collaboration with product owners, analysts or QAs.
Furthermore it works great to kinda specify the surface behavior and then implement it in the code rather than have more overall focus on the implementation.
Another good reason is that the application will be documented and designed around the behavior a user expects to experience when interacting with it.
We found it difficult to create a behavior implementation in BDD without having a user to interact with an interface. Therefore creating a given when then scenario without a user made it more challenging to communicate with the customer.
It surprised us that we had to combine normal language and then convert it to a programming language. It surprised us as well how agile this approach is and therefore focus was much more on the behavior than the actual implementation.
Yes indeed, it works great by specifying what behavior you expect for each feature, and therefore kinda gives you clear visibility of what is expected.
Yes as a developer we are rather used to focus on the development of individual components rather having a similar process just on the level of features.