Re: [Apache Bloodhound] #388: Test environment isolation across product boundaries - after #355
#388: Test environment isolation across product boundaries - after #355 ---+ Reporter: olemis| Owner: rjollos Type: task | Status: review Priority: critical | Milestone: Release 8 Component: multiproduct |Version: Resolution:| Keywords: product environment testing QA ---+ Comment (by olemis): Replying to [comment:8 rjollos]: [...] A related issue is that, since `process_request` is checking for `TICKET_CREATE` permission, the user must have `TICKET_CREATE` for their current scope in order to use the QCT. this is by design , if creating a ticket via QCT user must be granted with TICKET_CREATE in both the active env and the target env . The former case is not a big deal since [source:trunk/bloodhound_theme/bhtheme/templates/bloodhound_theme.html@1553998:339-356 QCT form is not displayed] . Nevertheless it must still be asserted in code to be consistent in case of direct requests hijacking system logic . [...] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/388#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #388: Test environment isolation across product boundaries - after #355
#388: Test environment isolation across product boundaries - after #355 ---+ Reporter: olemis| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: Release 8 Component: multiproduct |Version: Resolution:| Keywords: product environment testing QA ---+ Comment (by olemis): Patches refreshed and [comment:3 patch order] updated . Please review the [http://pastebin.com/ziejr5iW test results] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/388#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #388: Test environment isolation across product boundaries - after #355
#388: Test environment isolation across product boundaries - after #355 ---+ Reporter: olemis| Owner: rjollos Type: task | Status: review Priority: critical | Milestone: Release 8 Component: multiproduct |Version: Resolution:| Keywords: product environment testing QA ---+ Changes (by olemis): * owner: olemis = rjollos * status: accepted = review -- Ticket URL: https://issues.apache.org/bloodhound/ticket/388#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #388: Test environment isolation across product boundaries - after #355
#388: Test environment isolation across product boundaries - after #355 ---+ Reporter: olemis| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: Release 8 Component: multiproduct |Version: Resolution:| Keywords: product environment testing QA ---+ Comment (by olemis): /me refreshing these patches ... -- Ticket URL: https://issues.apache.org/bloodhound/ticket/388#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #388: Test environment isolation across product boundaries - after #355
#388: Test environment isolation across product boundaries - after #355
---+
Reporter: olemis| Owner: olemis
Type: task | Status: accepted
Priority: critical | Milestone: Release 8
Component: multiproduct |Version:
Resolution:| Keywords: product environment testing QA
---+
Comment (by olemis):
I have attached two patches implementing a test case and code to filter
product list to keep only those allowing `TICKET_CREATE` permission to
logged in user. Details :
{{{#!sh
$ hg qapplied
t387/t387_r1495238_attach_btn_value.diff
t387/t387_r1495238_functional_test.2.diff
t387/t387_r1495238_functional_test.3.diff
t387/t387_r1514232_functional_test.4.diff
t387/t387_r1514860_functional_test.5.diff
t387/t387_r1515319_functional_test.6.diff
t387/t387_r1515319_functional_test.7.diff
t387/t387_r1526822_functional_test.8.diff
t387/t387_r1529237_functional_test.9.diff
t598/t598_r1510975_new_product_intertracwiki.diff
t598/t598_r1510975_functional_tester_product.diff
t598/t598_r1510975_test_new_product.diff
t669/t669_r1525378_product_edit.tests.diff
t667/t667_r1526822_error_mainnav.tests.diff
t388/t388_r1529237_ticket_perms_qct.tests.diff
t388/t388_r1529237_ticket_perms_qct.diff
$ hg log -r qparent
changeset: 462:83711e80eaca
tag: qparent
tag: svn-1529237
parent: 459:830ce7f6f3a5
user:gjm@13f79535-47bb-0310-9956-ffa450edef68
date:Fri Oct 04 17:46:05 2013 +
summary: updating the ticket timeline arrow of time and event grouping
- towards #687
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/388#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #388: Test environment isolation across product boundaries - after #355
#388: Test environment isolation across product boundaries - after #355 ---+ Reporter: olemis| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: Release 8 Component: multiproduct |Version: Resolution:| Keywords: product environment testing QA ---+ Comment (by olemis): BTW, the test case takes some time to be executed , so speed optimizations might be added afterwards if appropriate . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/388#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
