So I checked in a change that did some refactoring and added unit tests for two classes that were previously not tested: http://src.chromium.org/viewvc/chrome?view=rev&revision=20836
According to the coverage graphs, that change actually brought both the source code and test code coverage *down*. What's interesting is the coverage analysis reports my new tests aren't being executed at all: http://build.chromium.org/buildbot/coverage/linux-debug/20836/CHROMIUM/media/filters/index.html Now I have no clue who/what process is generating these numbers, but maybe it needs to be clobbered. Andrew --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
