You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/06/13 17:51:12 UTC

Re: [Apache Bloodhound] #387: Rewrite Trac functional test cases against product environments - after #355

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

Comment (by olemis):

 Patches attached to this ticket are an early preview of the work made to
 rewrite Trac functional test suite . Details below

 {{{#!sh

 $ hg qapplied
 t509/t509_r1480735_mp_class_test_setup.diff
 t509/t509_r1477773_tracadmin_globalcmd_attr.diff
 t514/t514_r1477773_load_bootstrap_handler.diff
 t514/t514_r1477773_tracd_bootstrap.diff
 t387/t387_r1487712_bloodhound_setup.diff
 t387/t387_r1485255_functional_test_infra.diff

 $ hg log -r qparent --template="[{svnrev}] - {desc}\n"
 [1492040] - Refs #201: Added license header that was missing from new file
 in  [1492038], fixed a truncated license header and moved license headers
 to top of template files to normalize position across all templates.

 }}}

 Differences between these two testing environments are documented in the
 docstrings of `BloodhoundFunctionalTester` class.

 Disclaimer : This is still work in progress . Major TODOs are :

   - Integrate the functional suite smoothly into the multi-product test
 suite .
   - Write loaders for functional test cases
   - Enable test discovery for functional test cases
   - Rewrite some test cases after updating Genshi templates to deal with
     [http://goo.gl/as0uU nested forms in ticket view] ,
     thus prematurely halting twill parser when trying to extract form data
   - Deal with package dependencies prior to running Bloodhound installer
 script
   - Transform current failures into successful test cases (see
 [http://goo.gl/FtZhi this spreadsheet])

 {{{#!sh
 $ python setup.py test -m tests.functional

 [...]

 -----------------------
 Ran 126 tests in 892.802s

 FAILED (failures=18, errors=18)

 }}}

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