#355: Run Trac test suite against product environments - after #115 #288
---------------------------+------------------------------------
Reporter: olemis | Owner: olemis
Type: task | Status: accepted
Priority: major | Milestone:
Component: multiproduct | Version:
Resolution: | Keywords: environment testing QA
---------------------------+------------------------------------
Comment (by olemis):
Replying to [comment:10 olemis]:
> Replying to [comment:7 jure]:
> > Replying to [comment:5 olemis]:
>
[...]
>
> > r1437357 solves that, but now tests are failing with the following
assertion:
> >
> [...]
>
> ~~ It seems to me that this is related to the issue mentioned in
comment:8:ticket:288 , but I'm not 100% sure ... yet ... ~~
>
> No it's not ... :-$
In the end this was happening because up to this point workflow definition
for product environments was empty .
[attachment:t115_r1437383_inherit_product_config.diff:ticket:115 A new
patch for #115] adds this functionality , thereby after applying patches
against r1437383 in this order
{{{
#!sh
$ hg qapplied
t115/t115_r1437383_inherit_product_config.diff
t115/t115_r1436300_option_accessor.diff
t355/t355_r1437383_trac_test_perm.diff
t355/t355_r1437383_trac_test_ticket_api.diff
}}}
... ticket API test report looks like this .
{{{
#!sh
$ python setup.py test -m tests.ticket.api
running test
running egg_info
writing BloodhoundMultiProduct.egg-info/PKG-INFO
writing top-level names to BloodhoundMultiProduct.egg-info/top_level.txt
writing dependency_links to BloodhoundMultiProduct.egg-
info/dependency_links.txt
writing entry points to BloodhoundMultiProduct.egg-info/entry_points.txt
writing BloodhoundMultiProduct.egg-info/PKG-INFO
writing top-level names to BloodhoundMultiProduct.egg-info/top_level.txt
writing dependency_links to BloodhoundMultiProduct.egg-
info/dependency_links.txt
writing entry points to BloodhoundMultiProduct.egg-info/entry_points.txt
reading manifest file 'BloodhoundMultiProduct.egg-info/SOURCES.txt'
writing manifest file 'BloodhoundMultiProduct.egg-info/SOURCES.txt'
running build_ext
test_available_actions_chgprop_only
(tests.ticket.api.ProductTicketSystemTestCase) ... ok
test_available_actions_create_only
(tests.ticket.api.ProductTicketSystemTestCase) ... ok
test_available_actions_full_perms
(tests.ticket.api.ProductTicketSystemTestCase) ... ok
test_available_actions_no_perms
(tests.ticket.api.ProductTicketSystemTestCase) ... ok
test_custom_field_optional_select
(tests.ticket.api.ProductTicketSystemTestCase) ... ok
test_custom_field_order (tests.ticket.api.ProductTicketSystemTestCase) ...
ok
test_custom_field_select (tests.ticket.api.ProductTicketSystemTestCase)
... ok
test_custom_field_text (tests.ticket.api.ProductTicketSystemTestCase) ...
ok
test_custom_field_textarea (tests.ticket.api.ProductTicketSystemTestCase)
... ok
----------------------------------------------------------------------
Ran 9 tests in 0.758s
OK
}}}
So I guess that after fixing the issue identified in comment:8:ticket:288
they should all be ready to be applied in `bep_0003_multiproduct` branch .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/355#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
