StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POBDD: SpecFlow - Scenario Outline Behaviour Not As Expected
primarykey
Id
12803207
data
AcceptedAnswerId
12804085
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-09T15:15:11.623
FavoriteCount
0
LastActivityDate
2012-10-09T16:22:25.920
LastEditDate
2012-10-09T16:22:25.920
LastEditorUserId
1590675
OwnerUserId
1590675
ParentId
0
PostTypeId
1
Score
0
ViewCount
1437
LastEditorDisplayName
text
Body
Using scenario outlines in SpecFlow, e.g. <pre><code>Scenario Outline: Invalid Login Details Given some pre-conditions... When user "Larry" enters username <username> and password <password> Then the message "Invalid Login Details" should be displayed Examples: |username|password| |larry06 | | |larry06 |^&*%*^$ | |%^&&** |pass123 | | |pass123 | </code></pre> I expected that the "When" step would be evaluated as such: <pre><code>public void WhenUserEntersUsernameAndPassword(String username, String password){} </code></pre> And that the scenario would be run 4 times - for each row of the table, passing the values as required. That's not the case. Instead, SpecFlow creates 1 of 4 required step definitions: <pre><code>[When(@"""(.*)"" provides the following new username larry(.*) and password ")] public void WhenUserEntersUsernameLarryAndPassword(string p0, int p1) { //TODO } </code></pre> And to get the remaining 3 to 'work' I need to manually write methods explicitly matching other values in the table. I've since realised that I can just say: <pre><code>When "Larry" enters username "<username>" and password "<password>" </code></pre> And I get: <pre><code>[When(@"""(.*)"" provides the following ""(.*)"" and ""(.*)""")] public void WhenUserEntersUsernameAndPassword(string p0, string name, string pass) { //TODO } </code></pre> Perfect. But all documentation seems to suggest I don't need "" and that should just work (e.g. <a href="https://github.com/cucumber/cucumber/wiki/Scenario-outlines" rel="nofollow">https://github.com/cucumber/cucumber/wiki/Scenario-outlines</a>). I note: <blockquote> "Your step definitions will never have to match a placeholder. They will need to match the values that will replace the placeholder" </blockquote> I just don't really see the value of writing separate step definitions for each line of the table. Is this nuance specific to SpecFlow?
Tags
<cucumber><bdd><specflow><gherkin>
Title
BDD: SpecFlow - Scenario Outline Behaviour Not As Expected
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USTom Tom
UserOwnerUserId
1. USTom Tom
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.