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.
openproject/modules/dashboards/spec/features/custom_text_spec.rb

184 lines
5.8 KiB

#-- copyright
# OpenProject is an open source project management software.
# Copyright (C) 2012-2021 the OpenProject GmbH
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License version 3.
#
# OpenProject is a fork of ChiliProject, which is a fork of Redmine. The copyright follows:
# Copyright (C) 2006-2013 Jean-Philippe Lang
# Copyright (C) 2010-2013 the ChiliProject Team
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
#
# See COPYRIGHT and LICENSE files for more details.
#++
require 'spec_helper'
require_relative '../support/pages/dashboard'
describe 'Project description widget on dashboard', type: :feature, js: true do
let!(:type) { FactoryBot.create :type_task, name: 'Task' }
let!(:project) do
FactoryBot.create :project, types: [type]
end
let(:permissions) do
%i[view_dashboards
manage_dashboards
add_work_packages
]
end
let(:role) do
FactoryBot.create(:role, permissions: permissions)
end
let(:user) do
FactoryBot.create(:user, member_in_project: project, member_with_permissions: permissions)
end
let(:dashboard_page) do
Pages::Dashboard.new(project)
end
let(:image_fixture) { ::UploadedFile.load_from('spec/fixtures/files/image.png') }
let(:editor) { ::Components::WysiwygEditor.new 'body' }
let(:field) { TextEditorField.new(page, 'description', selector: '.inline-edit--active-field') }
before do
login_as user
end
context 'for a user having edit permissions' do
before do
dashboard_page.visit!
end
it 'can use the wp create button macro within it' do
dashboard_page.add_widget(1, 1, :within, "Custom text")
sleep(0.1)
# As the user lacks the manage_public_queries and save_queries permission, no other widget is present
custom_text_widget = Components::Grids::GridArea.new('.grid--area.-widgeted:nth-of-type(1)')
within custom_text_widget.area do
find('.inplace-editing--container ').click
end
editor.insert_macro 'Insert create work package button'
expect(page).to have_selector('.op-modal')
select 'Task', from: 'selected-type'
find('.op-modal--submit-button').click
field.save!
dashboard_page.expect_and_dismiss_notification message: I18n.t('js.notice_successful_update')
within('#content') do
expect(page).to have_selector("a[href=\"/projects/#{project.identifier}/work_packages/new?type=#{type.id}\"]")
end
end
it 'can add the widget set custom text and upload attachments' do
dashboard_page.add_widget(1, 1, :within, "Custom text")
sleep(0.1)
# As the user lacks the manage_public_queries and save_queries permission, no other widget is present
custom_text_widget = Components::Grids::GridArea.new('.grid--area.-widgeted:nth-of-type(1)')
within custom_text_widget.area do
find('.inplace-editing--container ').click
field.set_value('My own little text')
field.save!
end
dashboard_page.expect_and_dismiss_notification message: I18n.t('js.notice_successful_update')
within custom_text_widget.area do
expect(page)
[31023] Preparation for project edit fields: Generalize edit and display fields currently work package specific (#7726) * Check edit fields for Work package dependencies * Make EditForm, NotificationService, EditContext indepenedent of Work Packages * Make EventsService independent of WorkPackages * Start renaming WpNotificationService (WiP) * Fix more references * Fix typescript errors * Add basic halEditingService * Rename to global halResourceEditingService (WiP) * Move typing from class to methods (WiP) * Fix typescript errors * Remove space in type * Add test project widget && generalize the editFieldGroup * Rename editing portal service [ci skip] * Rename WpEditFieldComponent * Rename WpDisplayFields * Rename display-XX-field to XX-display-field [ci skip] * Add WP specific ID field to distinguish between resources * Re-add state in work package resource * Generalize display field renderer * Rename spent-time to wp-spent-time and fix highlight specifics [ci skip] * Actually load the project schema and make field editable * Make edit-field-group.component an edit-form.component and subclass EditForm * Remove edit context in favor of specialized EditForm * Add special cases for work package editing * Fix edit actions bar * Fix codeclimate issues * Use WorkPackageNotificationService if necessary * Override NotificationService for WPs to allow WP specififc notifications (WiP) * Correctly provide wpNotification service Because the ui-router doesn't seem to correctly use the parent element's injector, we need to provide the wpNotification service not in the wp-base, but rather the wp-list component as well as in the isolated query space. * Allow to filter halEvents for specific resourceTypes (e.g. WorkPackage) * Remove superfluous cell class constant * Start renaming selectors for wp-edit-field into generics * Remove wp-table--cell-span in favor of display field selector * Consolidate other display and edit field styles * Provide specialized service for transitions in active edit forms * Remove superfluous overflowSelector * Accept that date field contains some work package specifics * Ignore unreadable files * Provide the changeset for work packages as a hook Since hal resource editing service is provided per query space, we cannot register them once (would only work globally) * Fix dangerfile * Remove another todo in halResourceNotification service * Fix npm TestBed for changed dependencies * Show inplace edit field in project details widget * Fix highlighting in single view * Provide HalResourceEditingService outside of project context * Used typedState for single-view * Also provide wpNotification service in split view * Correct check for resource type in eventsService * Fix getSchemaName in display field renderer * Fix passing ids into `halEditing.stopEditing` * Do not globally inject the halResourceEditingService There's a bug(?) in ui-router that gives you the global service before the parent injected service for a ui-view * Fix wpCreate service on copying and parallel creation * Remove test project widget * Revert changes for project details widget
5 years ago
.to have_selector('.inline-edit--display-field', text: 'My own little text')
find('.inplace-editing--container').click
field.set_value('My new text')
field.cancel_by_click
expect(page)
[31023] Preparation for project edit fields: Generalize edit and display fields currently work package specific (#7726) * Check edit fields for Work package dependencies * Make EditForm, NotificationService, EditContext indepenedent of Work Packages * Make EventsService independent of WorkPackages * Start renaming WpNotificationService (WiP) * Fix more references * Fix typescript errors * Add basic halEditingService * Rename to global halResourceEditingService (WiP) * Move typing from class to methods (WiP) * Fix typescript errors * Remove space in type * Add test project widget && generalize the editFieldGroup * Rename editing portal service [ci skip] * Rename WpEditFieldComponent * Rename WpDisplayFields * Rename display-XX-field to XX-display-field [ci skip] * Add WP specific ID field to distinguish between resources * Re-add state in work package resource * Generalize display field renderer * Rename spent-time to wp-spent-time and fix highlight specifics [ci skip] * Actually load the project schema and make field editable * Make edit-field-group.component an edit-form.component and subclass EditForm * Remove edit context in favor of specialized EditForm * Add special cases for work package editing * Fix edit actions bar * Fix codeclimate issues * Use WorkPackageNotificationService if necessary * Override NotificationService for WPs to allow WP specififc notifications (WiP) * Correctly provide wpNotification service Because the ui-router doesn't seem to correctly use the parent element's injector, we need to provide the wpNotification service not in the wp-base, but rather the wp-list component as well as in the isolated query space. * Allow to filter halEvents for specific resourceTypes (e.g. WorkPackage) * Remove superfluous cell class constant * Start renaming selectors for wp-edit-field into generics * Remove wp-table--cell-span in favor of display field selector * Consolidate other display and edit field styles * Provide specialized service for transitions in active edit forms * Remove superfluous overflowSelector * Accept that date field contains some work package specifics * Ignore unreadable files * Provide the changeset for work packages as a hook Since hal resource editing service is provided per query space, we cannot register them once (would only work globally) * Fix dangerfile * Remove another todo in halResourceNotification service * Fix npm TestBed for changed dependencies * Show inplace edit field in project details widget * Fix highlighting in single view * Provide HalResourceEditingService outside of project context * Used typedState for single-view * Also provide wpNotification service in split view * Correct check for resource type in eventsService * Fix getSchemaName in display field renderer * Fix passing ids into `halEditing.stopEditing` * Do not globally inject the halResourceEditingService There's a bug(?) in ui-router that gives you the global service before the parent injected service for a ui-view * Fix wpCreate service on copying and parallel creation * Remove test project widget * Revert changes for project details widget
5 years ago
.to have_selector('.inline-edit--display-field', text: 'My own little text')
end
dashboard_page.expect_no_notification message: I18n.t('js.notice_successful_update')
within custom_text_widget.area do
# adding an image
find('.inplace-editing--container').click
sleep(0.1)
end
# The drag_attachment is written in a way that it requires to be executed with page on body
# so we cannot have it wrapped in the within block.
editor.drag_attachment image_fixture.path, 'Image uploaded'
within custom_text_widget.area do
expect(page).to have_selector('attachment-list-item', text: 'image.png')
expect(page).to have_no_selector('notifications-upload-progress')
field.save!
end
dashboard_page.expect_and_dismiss_notification message: I18n.t('js.notice_successful_update')
within custom_text_widget.area do
expect(page)
.to have_selector('#content img', count: 1)
expect(page)
.to have_no_selector('attachment-list-item', text: 'image.png')
end
end
end
context 'for a user lacking edit permissions' do
let!(:dashboard) do
FactoryBot.create(:dashboard_with_custom_text, project: project)
end
let(:permissions) do
%i[view_dashboards]
end
before do
dashboard_page.visit!
end
it 'allows reading but not editing the custom text' do
custom_text_widget = Components::Grids::GridArea.new('.grid--area.-widgeted:nth-of-type(1)')
within custom_text_widget.area do
expect(page)
.to have_content(dashboard.widgets.first.options[:text])
expect(page)
.to have_no_selector('.inplace-editing--container')
end
end
end
end