title: How to identify scenarios and steps with numerical ids on cucumber?
body: <h2>Looking into a nice approach for identifying scenarios and steps with numerical ids on cucumber</h2>
  
  <ul>
  <li>Don't want to use code line number for this, that can change after editing features.</li>
  <li>I'm already using tags to identify/group scenarios but customer requires a unique number to refer them.</li>
  <li>Ideal solution would take care of this automagically perhaps a cucumber gem with some sort of persistence support.</li>
  </ul>
  
  <p>As of now, i will simply use tags with hard-coded numerical ids on it, e.g.</p>
  
  <pre><code>@login @tc10100
  Scenario: Login with wrong credentials
    Given I am not logged in
    And I go to the user signin page
    #and so on...
  </code></pre>
  
  <p>Notes about this temporary tagged (@tc10100) solution:</p>
  
  <ul>
  <li>tc stands for Test Case (customer is accustomed to that term)</li>
  <li>10100 is just some initial case number</li>
  <li>since a good designed scenario will not include more than 9 steps, step numbers will be counted automatically, starting on step 1, 2, 3... So @tc10100 step 2 is "And I go to the user signin page"</li>
  </ul>