Re: [Apache Bloodhound] #772: Many multiproduct test modules can't be executed in isolation

[Apache Bloodhound <de...@bloodhound.apache.org>]

#772: Many multiproduct test modules can't be executed in isolation
---------------------------+--------------------
  Reporter:  rjollos       |      Owner:  olemis
      Type:  defect        |     Status:  closed
  Priority:  major         |  Milestone:
 Component:  multiproduct  |    Version:
Resolution:  worksforme    |   Keywords:
---------------------------+--------------------
Changes (by olemis):

 * status:  accepted => closed
 * resolution:   => worksforme


Comment:

 In my local environment this works for me considering the quick tests
 shown below. Please check whether this is related to some local
 configuration and, if the problem persists then feel free to reopoen it .
 I'm not able to reproduce it atm though .

 This is the recommended way to do it .

 {{{#!sh

 $ python setup.py test -m tests.attachment
 running test
 running egg_info
 writing requirements to BloodhoundMultiProduct.egg-info/requires.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_delete (tests.attachment.ProductAttachmentTestCase) ... ok
 test_delete_file_gone (tests.attachment.ProductAttachmentTestCase) ... ok
 test_get_path (tests.attachment.ProductAttachmentTestCase) ... ok
 test_get_path_encoded (tests.attachment.ProductAttachmentTestCase) ... ok
 test_insert (tests.attachment.ProductAttachmentTestCase) ... ok
 test_insert_outside_attachments_dir
 (tests.attachment.ProductAttachmentTestCase) ... ok
 test_insert_unique (tests.attachment.ProductAttachmentTestCase) ... ok
 test_legacy_permission_on_parent
 (tests.attachment.ProductAttachmentTestCase)
 Ensure that legacy action tests are done on parent.  As ... ok
 test_path_extension (tests.attachment.ProductAttachmentTestCase) ... ok
 test_product_path_isolation (tests.attachment.ProductAttachmentTestCase)
 ... ok
 test_reparent (tests.attachment.ProductAttachmentTestCase) ... ok
 test_resource_doesnt_exist (tests.attachment.ProductAttachmentTestCase)
 ... ok
 test_resource_exists (tests.attachment.ProductAttachmentTestCase) ... ok
 test_select_empty (tests.attachment.ProductAttachmentTestCase) ... ok

 ----------------------------------------------------------------------
 Ran 14 tests in 0.498s

 OK

 }}}

 More information in [http://pastebin.com/KqBEe0Us this detailed shell
 session] .

 Initially I was tempted to close this ticket but noticed that some modules
 do not yield the same results if they are executed independently . Compare
 [http://pastebin.com/KqBEe0Us independent tests reports] vs
 [http://pastebin.com/1Kz1Nhq8 the whole test suite] . Is this what you
 mean ? If so , let's keep this ticket open , otherwise let's close it and
 fix each failure in a separate (more specific) ticket . Nevertheless the
 specific module you tried really works for me .

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