gitlab-org--gitlab-foss/features/dashboard/dashboard.feature

@dashboard
Feature: Dashboard
  Background:
    Given I sign in as a user
    And I own project "Shop"
    And project "Shop" has push event
    And I visit dashboard page

  @javascript
  Scenario: I should see projects list
    Then I should see "New Project" link
    Then I should see "Shop" project link
    Then I should see project "Shop" activity feed

  Scenario: I should see groups list
    Given I have group with projects
    And I visit dashboard page
    Then I should see groups list

  @javascript
  Scenario: I should see last push widget
    Then I should see last push widget
    And I click "Create Merge Request" link
    Then I see prefilled new Merge Request page

  @javascript
  Scenario: I should see User joined Project event
    Given user with name "John Doe" joined project "Shop"
    When I visit dashboard page
    Then I should see "John Doe joined project Shop" event

  @javascript
  Scenario: I should see User left Project event
    Given user with name "John Doe" joined project "Shop"
    And user with name "John Doe" left project "Shop"
    When I visit dashboard page
    Then I should see "John Doe left project Shop" event
Splitted the Spinach tests to prevent time-outs Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com> 2014-06-04 16:55:27 -04:00			`@dashboard`
Cucumber -> Dashboard features 2012-06-16 05:50:14 -04:00			`Feature: Dashboard`
rewrite dashboard feature steps using spinach 2012-09-10 04:51:02 -04:00			`Background:`
			`Given I sign in as a user`
Cucumber -> Dashboard features 2012-06-16 05:50:14 -04:00			`And I own project "Shop"`
			`And project "Shop" has push event`
rewrite dashboard feature steps using spinach 2012-09-10 04:51:02 -04:00			`And I visit dashboard page`
Cucumber -> Dashboard features 2012-06-16 05:50:14 -04:00
Speedup dashboard via loading events with ajax 2013-01-07 07:36:01 -05:00			`@javascript`
Cucumber -> Dashboard features 2012-06-16 05:50:14 -04:00			`Scenario: I should see projects list`
			`Then I should see "New Project" link`
			`Then I should see "Shop" project link`
			`Then I should see project "Shop" activity feed`

Spianch test for group dashboard 2012-10-03 06:42:17 -04:00			`Scenario: I should see groups list`
			`Given I have group with projects`
			`And I visit dashboard page`
			`Then I should see groups list`

Merge Request on forked projects The good: - You can do a merge request for a forked commit and it will merge properly (i.e. it does work). - Push events take into account merge requests on forked projects - Tests around merge_actions now present, spinach, and other rspec tests - Satellites now clean themselves up rather then recreate The questionable: - Events only know about target projects - Project's merge requests only hold on to MR's where they are the target - All operations performed in the satellite The bad: - Duplication between project's repositories and satellites (e.g. commits_between) (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos) Fixes: Make test repos/satellites only create when needed -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap) -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually -fixed remote removal -How to merge renders properly -Update emails to show project/branches -Edit MR doesn't set target branch -Fix some failures on editing/creating merge requests, added a test -Added back a test around merge request observer -Clean up project_transfer_spec, Remove duplicate enable/disable observers -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well -Signifant speed ups for tests -Update formatting ordering in notes_on_merge_requests -Remove wiki schema update Fixes for search/search results -Search results was using by_project for a list of projects, updated this to use in_projects -updated search results to reference the correct (target) project -udpated search results to print both sides of the merge request Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8 2013-04-25 10:15:33 -04:00			`@javascript`
Remove duplicate coverage in spec requests. All features should be covered in cucumber 2012-08-03 12:29:54 -04:00			`Scenario: I should see last push widget`
Cucumber -> Dashboard features 2012-06-16 05:50:14 -04:00			`Then I should see last push widget`
			`And I click "Create Merge Request" link`
			`Then I see prefilled new Merge Request page`

Speedup dashboard via loading events with ajax 2013-01-07 07:36:01 -05:00			`@javascript`
User joined project event added 2012-09-09 16:18:28 -04:00			`Scenario: I should see User joined Project event`
			`Given user with name "John Doe" joined project "Shop"`
			`When I visit dashboard page`
Fix specs. 2015-02-13 07:48:27 -05:00			`Then I should see "John Doe joined project Shop" event`
User left project event added 2012-09-09 17:27:47 -04:00
Speedup dashboard via loading events with ajax 2013-01-07 07:36:01 -05:00			`@javascript`
User left project event added 2012-09-09 17:27:47 -04:00			`Scenario: I should see User left Project event`
			`Given user with name "John Doe" joined project "Shop"`
			`And user with name "John Doe" left project "Shop"`
			`When I visit dashboard page`
Fix specs. 2015-02-13 07:48:27 -05:00			`Then I should see "John Doe left project Shop" event`