kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/features/project/commits/commits.feature

48 lines
1.4 KiB
Gherkin
Raw Normal View History

rewrite project commits features using spinach
2012-09-10 07:27:11 -04:00
Feature: Project Browse commits
Background:
Given I sign in as a user
Speed up Compare feature step
2012-09-26 13:58:50 -04:00
And I own a project
And I visit my project's commits page
Cucumber: * Profile * Browse code * Sceleton for main features * Wiki * Commits
2012-06-15 00:15:28 -04:00
Scenario: I browse commits list for master branch
Then I see project commits
Scenario: I browse atom feed of commits list for master branch
Given I click atom feed link
Then I see commits atom feed
Scenario: I browse commit from list
Given I click on commit link
Then I see commit info
diff view on commit with parallel diff view TODO: fix comment forms to respect left and right columns
2013-10-09 16:22:37 -04:00
And I see parallel diff button
Scenario: I browse commit with parallel diff view
Given I click on commit link
And I click parallel diff button
Then I see unified diff button
Cucumber: * Profile * Browse code * Sceleton for main features * Wiki * Commits
2012-06-15 00:15:28 -04:00
Scenario: I compare refs
Given I visit compare refs page
And I fill compare fields with refs
Speed up Compare feature step
2012-09-26 13:58:50 -04:00
Then I see compared refs
Add Spinach feature for Commit breadcrumbs
2012-11-01 17:57:44 -04:00
Scenario: I browse commits for a specific path
Given I visit my project's commits page for a specific path
Then I see breadcrumb links
Added feature test for stats
2012-11-10 16:33:10 -05:00
Scenario: I browse commits stats
Given I visit my project's commits stats page
Then I see commits stats
Improved large commit handling. Previously, only number of changed files mattered. Now, number of lines to render in the diff are also taken into account. A hard limit is set, above which diffs are not rendered and users are not allowed to override that. This prevents high server resource usage with huge commits. Related to #1745, #2259 In addition, handle large commits for MergeRequests and Compare controllers. Also fixes a bug where diffs are loaded twice, if user goes directly to merge_requests/:id/diffs URL.
2013-09-04 03:33:09 -04:00
Scenario: I browse big commit
Given I visit big commit page
Then I see big commit warning
Scenario: I browse huge commit
Given I visit huge commit page
Then I see huge commit message
Fix bug with rendering changing images in commits When viewing the diff for a changed image file, two bugs occur: - Both the 'before' and 'after' images link to the 'after' commit - Visiting the link for either image will cause a error The first is caused by both image links referencing '@commit.id' rather than '@commit.parent_id'. The second is caused by the use of 'project_tree_path' which is used for creating links to directories in the git file tree. 'project_blob_path' which links to files should be used instead.
2013-09-10 21:36:04 -04:00
Scenario: I browse a commit with an image
Given I visit a commit with an image that changed
Then The diff links to both the previous and current image
Copy permalink