Databases
StackOverflow2013
Postsdbo
POBDD: Explicit Examples - Appropriate Pronouns?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBDD: Explicit Examples - Appropriate Pronouns?
    text
    copied!<p>When writing scenarios, does anyone have a strong argument for choosing one of the following styles over another?</p> <pre><code>Feature: Search Product As a customer I want to search for a product So that I can easily locate what I want to purchase Scenario: Multiple Products Found (First Person Style) Given the following products exist: |Product | |Normal Orange| |Large Orange | When I search for "orange" &lt;--- Then the system should display the following products: |Product | |Normal Orange| |Large Orange | </code></pre> <p>Or...</p> <pre><code>Scenario: Multiple Products Found (Generic Third Person Style) Given the following products exist: |Product | |Normal Orange| |Large Orange | When the customer searches for "orange" &lt;--- Then the system should display the following products: |Product | |Normal Orange| |Large Orange | </code></pre> <p>Or...</p> <pre><code>Scenario: Multiple Products Found (Specific Person Style) Given the following products exist: |Product | |Normal Orange| |Large Orange | When "John" searches for "orange" &lt;--- Then the system should display the following products: |Product | |Normal Orange| |Large Orange | </code></pre> <p>They all seem to work just fine - I wonder if I'm missing an obvious pitfall, as so many examples seem to use specific values for the actors (not just specific values for inputs / outcomes).</p> <p>My only argument against using:</p> <pre><code>When the customer searches for "orange" </code></pre> <p>is that separate, equivalent steps would have to be defined if other actors could also use the same function.</p> <p>Personally, I think "I" reads quite well (though I feel like I know otherwise). Thoughts?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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