TheDude
/
openproject
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
OpenProject is the leading open source project management software.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
133 Commits
139 Branches
203 Tags
1.2 GiB
Tag: Branch: Tree: d8f2c1b5eb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd8f2c1b5eb'
${ noResults }
openproject/features/blocks.feature

86 lines
4.2 KiB
Raw Normal View History Unescape

Preparing the gem for release; adding project-scoped blocks from other plugins Following the guidelines in https://www.openproject.org/projects/openproject/wiki/Developing_Plugins, the gem was prepared for release * added copyright-headers * added readme * gemspec extended This also fixes an issue with plugins, that want to add views for the my_project_page: The mechanism now looks for blocks in the my_projects_overviews-folder of the plugin and adds them to the configuration using the document's name (Very similar to the way my_page does this in core.) An example for this can be found in the documents-plugin, which now provides views that either show all documents the user can see (in my/_documents.html.erb) and scoped to the given project (under my_projects_overviews/_project_documents.html.erb)
11 years ago
#-- copyright
# OpenProject is a project management system.
#
# Copyright (C) 2012-2013 the OpenProject Team
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License version 3.
#
# See doc/COPYRIGHT.rdoc for more details.
#++
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
Feature: Behavior of specific blocks (news, issues - this is currently not complete!!)
Background:
Given there is 1 project with the following:
| name | tested_project |
And the project "tested_project" has the following types:
| name | position |
| Bug | 1 |
And there is 1 project with the following:
| name | other_project |
And the project "other_project" has the following types:
| name | position |
| Bug | 1 |
And there is 1 user with the following:
| login | bob |
And there is 1 user with the following:
| login | mary |
And there is a role "member"
And the role "member" may have the following rights:
| view_work_packages |
| create_issues |
And the user "bob" is a "member" in the project "tested_project"
And the user "bob" is a "member" in the project "other_project"
And I am logged in as "bob"
Scenario: In the news Section, I should only see news for the selected project
And project "tested_project" uses the following modules:
| news |
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And the following widgets are selected for the overview page of the "tested_project" project:
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
#TODO mapping from the human-name back to it's widget-name??!
| top | news |
Given there is a news "test-headline" for project "tested_project"
And there is a news "NO-SHOW" for project "other_project"
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And I am on the homepage for the project "tested_project"
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
Then I should see the widget "news"
And I should see the news-headline "test-headline"
And I should not see the news-headline "NO-SHOW"
Scenario: In the 'Issues reported by me'-Section, I should only see issues for the selected project
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And there are the following issues with attributes:
| subject | project | author |
| Test-Issue | tested_project | bob |
| NO-SHOW | other_project | bob |
And the following widgets are selected for the overview page of the "tested_project" project:
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
| top | issuesreportedbyme |
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And I am on the homepage for the project "tested_project"
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
Then I should see the widget "issuesreportedbyme"
And I should see the issue-subject "Test-Issue" in the 'Issues reported by me'-section
And I should not see the issue-subject "NO-SHOW" in the 'Issues reported by me'-section
Scenario: In the 'Issues assigned to me'-Section, I should only see issues for the selected project
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And there are the following issues with attributes:
| subject | project | author | assignee |
| Test-Issue | tested_project | bob | bob |
| NO-SHOW | tested_project | bob | mary |
And the following widgets are selected for the overview page of the "tested_project" project:
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
| top | issuesassignedtome |
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And I am on the homepage for the project "tested_project"
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
Then I should see the widget "issuesassignedtome"
And I should see the issue-subject "Test-Issue" in the 'Issues assigned to me'-section
And I should not see the issue-subject "NO-SHOW" in the 'Issues assigned to me'-section
Scenario: In the 'Issues watched by me'-Section, I should only see issues for the selected project
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And there are the following issues with attributes:
| subject | project | author | watched_by |
| Test-Issue | tested_project | bob | bob |
| NOT-WATCHED | other_project | bob | bob,mary |
And the following widgets are selected for the overview page of the "tested_project" project:
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
| top | issueswatched |
Added the remaing features (delete Attachments) and worked in the annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy
11 years ago
And I am on the homepage for the project "tested_project"
added some cukes to test, that the blocks are actually limited to the selected project. Also did some housecleaning(e.g. remove unused hooks)
11 years ago
Then I should see the widget "issueswatched"
And I should see the issue-subject "Test-Issue" in the 'Issues watched'-section
And I should not see the issue-subject "NOT-WATCHED" in the 'Issues watched'-section