Bug 77052 - PerformanceTests/Mutation should be moved to PerformanceTests/DOM/MutationObserver
Summary: PerformanceTests/Mutation should be moved to PerformanceTests/DOM/MutationObs...
Status: RESOLVED LATER
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-25 14:51 PST by Ryosuke Niwa
Modified: 2012-10-08 15:53 PDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2012-01-25 14:51:51 PST 
"Mutation" isn't really a descriptive name for these tests as they're specifically testing the performance of mutation observers.
Comment 1 Adam Barth 2012-01-25 14:57:52 PST 
Can it be  PerformanceTests/DOM/MutationObserver ?
Comment 2 Adam Klein 2012-01-25 14:59:49 PST 
Either of the proposed names sounds good to me.
Comment 3 Ryosuke Niwa 2012-01-25 15:03:04 PST 
(In reply to comment #1)
> Can it be  PerformanceTests/DOM/MutationObserver ?

Yeah. That's more pleasing to eyes but I don't think we normally use CamelCase for subdirectories though. e.g. we have "resources" directories instead of "Resources", and WebCore/editing instead of WebCore/Editing.
Comment 4 Zoltan Horvath 2012-09-22 01:05:28 PDT 
I prefer camelcase style, but what is our conclusion now?
Comment 5 Ryosuke Niwa 2012-09-22 11:10:29 PDT 
(In reply to comment #4)
> I prefer camelcase style, but what is our conclusion now?

We should probably just use CamelCase. On somewhat related note, I don't think we should have nested directory structures in PerformanceTests if we wanted to use Datazilla (Mozilla's new perf-o-matic).