#387: Rewrite Trac functional test cases against product environments - after
#355
-------------------------+-------------------------------------------------
  Reporter:  olemis      |      Owner:  rjollos
      Type:  task        |     Status:  review
  Priority:  major       |  Milestone:  Release 8
 Component:              |    Version:
  multiproduct           |   Keywords:  product environment functional
Resolution:              |  testing QA
-------------------------+-------------------------------------------------

Comment (by olemis):

 I have added a new patch to achieve some (explicit) uniformity when
 dealing with functional tester methods in global env context (see #388 for
 sample test cases relying on it) . After recent commits this is what my
 local patch looks like

 {{{#!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
 t598/t598_r1510975_functional_tester_product.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
 t387/t387_r1524640_no_r5994.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 +0000
 summary:     updating the ticket timeline arrow of time and event grouping
 - towards #687

 }}}

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/387#comment:29>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Reply via email to