added cukes for debug mode being enabled depending on whether we run in production mode or not

git-svn-id: https://dev.finn.de/svn/cockpit/branches/reporting_merge@2151 7926756e-e54e-46e6-9721-ed318f58905e
pull/6827/head
p.tessenow 14 years ago
parent 240df99ee6
commit 6f5a1a26b2
  1. 21
      features/permissions.feature

@ -2,5 +2,22 @@ Feature: Permissions
#XXX: Test permissions on table and simple table (currently testet in _cost_entry_table partial only) #XXX: Test permissions on table and simple table (currently testet in _cost_entry_table partial only)
#XXX: Test access permissions for /cost_reports AND /project/../cost_reports - sometimes there is access denied where is should not and vice versa #XXX: Test access permissions for /cost_reports AND /project/../cost_reports - sometimes there is access denied where is should not and vice versa
Scenario: Coming to the cost report for the first time, I should see my entries @changes_environment
Given there is a standard cost control project named "Standard Project" Scenario: Enabling the debug-flag doesn't work in production mode
When we can finally switch the ruby environment within our cukes
Given there is a standard permission test project named "Permission_Test"
And I am in "production" mode
And I am admin
And I am on the overall Cost Reports page with standard groups in debug mode
And I start debugging
Then I should not see "[ RESULT ]"
And I should not see "[ Query ]"
@changes_environment
Scenario: Enabling the debug-flag works in development mode
Given there is a standard permission test project named "Permission_Test"
And I am in "development" mode
And I am admin
And I am on the overall Cost Reports page with standard groups in debug mode
Then I should see "[ RESULT ]"
And I should see "[ Query ]"
Loading…
Cancel
Save