Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can put "IMHO" after every paragraph in this answer. This is my experience after doing BDD / Specification by example for four years.</p> <p>BDD is about communication. BDD is about understanding each other in the entire team. </p> <p>Cucumber is (just) a tool that facilitates communication. The only reason to use Cucumber (and the extra abstractions it adds) is because it will make it easier to understand each other than other formats. If we were only developers in the team we would probably be better off using code. </p> <p>So, to answer your question, if your BA's and customers understand GET, POST etc then it might be appropriate to use that in the specification. But beware that you've just tied the specification to the implementation. Changes will propagate even into the Cucumber scenarios. </p> <p>More likely your first example is format that your customers and BA's can relate to and understand straight off. </p> <p>But, of course, it depends on the level of technical details your non-technical team members are using. Make it easy for everyone to understand. </p> <p>BDD is about communication. </p> <p>Here's some presentations on the subject that I've found both useful and in one case thoroughly entertaining: </p> <ul> <li><a href="http://skillsmatter.com/podcast/agile-scrum/bdd-as-its-meant-to-be-done" rel="nofollow">BDD as you meant it</a></li> <li><a href="http://skillsmatter.com/podcast/agile-testing/refuctoring-your-cukes" rel="nofollow">Refuctore your Cukes</a></li> <li><a href="http://skillsmatter.com/podcast/agile-testing/cuke-envy-a-dot-net-programmers-attempt-to-catch-up" rel="nofollow">Cuke Envy</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POShould API REST BDD Cucumbers Gherkins include specific details about an API or data
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMarcus Hammarberg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the comment. I'm particularly interested in your mention about coupling your implementation with your design. While it's highly unlikely a project will move from a RESTful design in the foreseeable future it is helpful that the implementation details are hidden in case the architecture does change.
      singulars
      1. PO
      1. USJames Murphy
    2. COI'd like to add that stepping back from implementation details can be helpful for *tech-only teams* as well. I've worked in such situations and it helped us think less about the technical side of things and focus more on the expected *behaviours* of the system we were describing.
      singulars
      1. PO
      1. USjbpros
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload