Feature: User Dashboard - user_dashboard_main.feature, user_dashboard_add_block.feature

tagging for sprint 1 - there's a lot involved and this may split into multiple files

Let's ensure what's here follows best practices. It may need to move into sprint 2 for actual completion.

At this time, I don't have a better plan. I am opening more issues today from jhodgdon that I think also touch on the dashboard but may not have time to link them in ... maybe you can keep an eye out for them and make this the Meta issue with links to any related issues you've found?

I am going to move this into the main project and that will put all our work in a single place.

I concur. Testing drag and drop should wait until next sprint.

This is the third issue that hasn't applied cleanly because of:

Checking patch features/bootstrap/FeatureContext.php...
error: while searching for:
  }else
    throw new Exception("No options/texts specified");
  }
}

There's plenty to clarify on this, and additionally by the time I have, then we'll probably have this issue fixed too. Assigning to me to sort out.

Setting to "Needs work"

I don't immediately see what commit this references. Can you point me in the right direction?

Updating meta data.

and again ... setting to feature/scenarios so I'll see it when I know where to look.

merged to master, but I think this has scenarios that need to be tagged dependent on preceding scenarios.

features/project/user_dashboard_main.feature has one consistently failing scenario ... it appears that "Your posts" is not on the page when the scenario begins and so it cannot be closed.

  Scenario: Check Close icon of the block # features/project/user_dashboard_main.feature:67
    When I close the block "Your Posts"   # FeatureContext::iCloseTheBlockFromDashboard()
      The block "Your Posts" cannot be found.
    Then I should not see the block       # FeatureContext::iShouldNotSeeTheBlock()

I updated the language to use the more formal "until" instead of 'till', updated the feature to better reflect business value and removed the @wip and @flaky tags. I also added I should not see 'Access denied' to the known failure since it better reflects the bug being encountered there.

Can you open a bug report that includes the specific steps to reproduce the problem in this queue and assign it to Senpai so he can move it to the right development queue? (Does this problem exist on production?)

I've marked this with the best status we have to indicate that this needs porting to the D7 branch, which I tried, but wasn't able to sort out at the moment.

I'm getting failures on D6 and D7 and it looks like, on D6 anyway, it's a problem with the test. Can you look into it?

:   Scenario: View the block: Your Posts                                                            # features/drupalorg/user_dashboard_main.feature:59
    Then I should see the block "Your Posts" in column "2"                                        # FeatureContext::iShouldSeeTheBlockInColumn()
    And I should see at least "3" items in block "Your Posts"                                     # FeatureContext::iShouldSeeAtLeastItemsInBlock()
      The block: Your Posts has only less than 3 items
    And I should see the following <icons> on the block "Your Posts"                              # FeatureContext::iShouldSeeTheFollowingOnTheBlock()
      | icons    |
      | Settings |
      | Close    |

  Scenario: Change number of items to show in a block                                               # features/drupalorg/user_dashboard_main.feature:67
    When I change the setting "Number of posts to show:" to "3" for the block "Your Posts" and save # FeatureContext::iChangeTheSettingToForTheBlockAndSave()
    Then I should see at least "3" items in block "Your Posts"                                      # FeatureContext::iShouldSeeAtLeastItemsInBlock()
      The block: Your Posts has only less than 3 items

  Scenario: Close the block                                                                         # features/drupalorg/user_dashboard_main.feature:71
    When I close the block "Your Posts"                                                             # FeatureContext::iCloseTheBlockFromDashboard()
    Then I should not see the block                                                                 # FeatureContext::iShouldNotSeeTheBlock()

7 scenarios (5 passed, 2 failed)
65 steps (62 passed, 1 skipped, 2 failed)

Looks like a great improvement! It would read better if we could create "x" issues, but we can pick that up when we work on the 7.x branch. I'm postponing this until the code base catches up and removing wip from the 6.x since these appear reliable.

http://drupal.org/node/1545884/commits

I think these are as far as they can go until D7 Drupal.org is ready for feedback.

Failing in appropriate places based on functionality

Adding a Next Steps section