Description David Williams 2014-11-17 08:07:05 EST

There's several bugs open already about problems with the "missing files" section at the end of unit tests results, and now with the "performance unit tests" being displayed, the problem was even worse, since with things as they are, there was a list of scores of them, even though we did not really expect them, to begin with. 

Some of this could be fixed by improved "testManifest" files, to better specify what is expected. But, would be nice to find a mostly automated way of determining this list. Perhaps take advantage of the "test.properties" file, generated during the build? 

In the mean time, I added a flag to the indexer, to "force" no "missing files" to be displayed -- simply the "lessor evil" solution, until a proper fix can be made.