[Webkit-unassigned] [Bug 49465] Enabling test expectations analyzer

Sun Nov 28 17:27:54 PST 2010

https://bugs.webkit.org/show_bug.cgi?id=49465

--- Comment #9 from David Levin <levin at chromium.org>  2010-11-28 17:27:54 PST ---
(In reply to comment #8)
> assign test case to bug more specifically (Ideally, one to one for testcase failure to bug rather than one bug associated many test case failures)

This is ideally what what your bug title should be. Here's my attempt (if I understood you correctly): "Assign bugs with test cases to failure chromium's test_expectations.txt"

Feel free to create a new bug with a title like this or something more accurate and if you wish, make this bug (49465) dependent on that new bug.

I hope that makes sense. The goal is to have the patch directly address the bug. Then people can look at the bug and tell what the patch is attempting to do. And this also usually means you ideally have one patch per bug in general.

When you post that patch in that bug, it would hopefully say something about bug numbers that were changed or why there is more than one bug assigned to some layout tests. (I'm guessing it means that there are multiple features needed for that test to succeed.)

For example: http/tests/media/remove-while-loading.html (had the original bug number removed but that bug number remains on other tests). (I'm guess it is because bug 13907 was too generic but then why does it remain on other tests which have another bug assigned like this one http/tests/security/local-video-poster-from-remote.htm).

I appreciate the way that you are breaking this up into small steps for patches. I'm just trying to help you to break up the bugs in a similar manner (and try to have the bug be self-contained). This will help others (like reviewers) understand things without getting familiar with everything you are doing. 

I hope this will give you a clear path to getting this done quickly!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.