StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12758877
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-06T10:18:05.850
FavoriteCount
0
LastActivityDate
2012-10-06T10:25:23.757
LastEditDate
2012-10-06T10:25:23.757
LastEditorUserId
1701085
OwnerUserId
1701085
ParentId
12719911
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think I'll go for option A. The thing is that BDD scenarios must serve as documentation of the system. So if a non technical wants to know how your discount system is working (A business guy, a tester or someone from the customer support team), they surely would like to know what it means to have a high volume of item and what it is the applied discount. And they would not want to have to go in the plumbing code to get this information back. I think this information is important and can not be hidden from the reader. Another benefit is that it will allow for a non developer (a tester for example) to write new scenarios and check what will happen if there are 1 item in the cart or 100 items. When you get too much abstract about thing, it gets harder to apply deliberate discovery. So with a scenario as in Option B, you loose the opportunity to ask your self these questions: <ul> <li>What happen if we have more than 50 items like 100 items is there any other discount available</li> <li>What happen if we have 1 item, surrely we need to not apply a discount or should we apply a discount based on the total price of the cart instead of the number of items in it, someone buying only one really expensive item should benefit a discount too ?</li> <li>is 10% the only available type of discount, do we have for example fixed amount discounts ? Do we have more complex discount strategies ?</li> </ul> When the business variable are visible, you can play around with them and figure out stuff that you may have forgotten or think about new interesting (or not) features. As a general rule, I'd hide what it does not matter to know in a scenario and in that case the number of items and the applied discount value do really matter to the reader.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow specific do I get in BDD scenarios?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USfoobarcode
UserOwnerUserId
1. USfoobarcode
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.