Comment 2 for bug 1317567

I think the issue is that when developing locally -- you run the tests and it destroys any data in your ES dev instance. Which means the developer then needs to re-ingest charms and bundles. The test suite doesn't need them itself. It creates a "temp_index" index to use, but then deletes the developers index in this one test. This has affected other CW devs, too. I was asked to comment it out when I isolated it as the culprit deleting developers working indexes. I don't understand what it is supposed to be testing.

perhaps it needs an @unittest.skipUnless(run_under_testini) or similar decoration.