And the program should return the Tm for the reaction according to [http://www.ncbi.nlm.nih.gov/pubmed/26244340/polymerase_rules]
A Bit About BDD
Enough is enough: do as much planning, analysis, and design as you need, but no more
Deliver stakeholder value: everything you write should contribute value to the feature/scenario
It's a behavior: everyone involved should have the same way of talking about the system and what it does.
- Accompanying mockups: sketches or visualistions of your desired program should accompany your user stories
- Accompanying definitions: as you add complexity, it may be necessary to begin logging definitions for complex terms
BDD in its grandest sense is about communication and viewing your software as a system with behaviour. When you are using BDD and Cucumber to specify projects for your team or other teams, you should develop it with others, and test your assumptions, and your teammates' responses to your documentation. Be flexible and have fun building them with each other!