Bug 44559

Summary: new-run-webkit-tests: clean up code for test_types, test_failures
Product: WebKit Reporter: Dirk Pranke <dpranke>
Component: New BugsAssignee: Dirk Pranke <dpranke>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, cjerdonek, eric, levin, ojan, tony
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Attachments:
Description Flags
Patch
none
Patch ojan: review+

Dirk Pranke
Reported 2010-08-24 15:21:10 PDT
new-run-webkit-tests: clean up code for test_types, test_failures
Attachments
Patch (17.50 KB, patch)
2010-08-24 15:22 PDT, Dirk Pranke
no flags
Patch (19.77 KB, patch)
2010-08-24 16:07 PDT, Dirk Pranke
ojan: review+
Dirk Pranke
Comment 1 2010-08-24 15:22:55 PDT
Eric Seidel (no email)
Comment 2 2010-08-24 15:34:52 PDT
Comment on attachment 65334 [details] Patch WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures.py:76 + raise NotImplementedError This is the new name? WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures_unittest.py:40 + failure_obj = FailureCrash() Why the local variables? Confused. WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures_unittest.py:37 + self.assertNotEqual(failure_obj.result_html_output('foo'), None) assertTrue would also work. This seems like not a very useful test. WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures_unittest.py:69 + self.assertRaises(NotImplementedError, failure_obj.message) I'm not sure the point of this test? WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:553 + output1 = fh1.read() This doesn't look like it would actually run. Is it tested? WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:555 + output2 = fh2.read() This either. Same typo. WebKitTools/Scripts/webkitpy/layout_tests/test_types/test_type_base_unittest.py:45 + if __name__ == '__main__': I think PEP8 says 2 blank lines between global blocks. WebKitTools/Scripts/webkitpy/layout_tests/test_types/text_diff.py:71 + if os.path.exists(filename): This is redundant. Just remove the indent.
Ojan Vafai
Comment 3 2010-08-24 15:43:54 PDT
Comment on attachment 65334 [details] Patch Nice cleanups. WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:553 + output1 = fh1.read() Shouldn't this be f1? Also, file_handle1 is more readable. WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:555 + output2 = fh2.read() ditto. WebKitTools/Scripts/webkitpy/layout_tests/test_types/text_diff.py:71 + if os.path.exists(filename): Don't need this if-statement given the one above.
Dirk Pranke
Comment 4 2010-08-24 15:50:42 PDT
(In reply to comment #2) > (From update of attachment 65334 [details]) > WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures.py:76 > + raise NotImplementedError > This is the new name? > Actually, the old name ("NotImplemented") was a typo, and such an exception does not exist. Good thing we always implmeented the routines :) > WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures_unittest.py:40 > + failure_obj = FailureCrash() > Why the local variables? Confused. No terribly compelling reason. I'll remove them. > > WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures_unittest.py:37 > + self.assertNotEqual(failure_obj.result_html_output('foo'), None) > assertTrue would also work. This seems like not a very useful test. > It's simply testing that the output isn't null. I don't particularly want to hard-code any specific output here, but I do care that we return something and the function is implemented. I could test for len(x) != 0; any other suggestions? > WebKitTools/Scripts/webkitpy/layout_tests/layout_package/test_failures_unittest.py:69 > + self.assertRaises(NotImplementedError, failure_obj.message) > I'm not sure the point of this test? > These checks test that the base class functions do in fact raise NotImplement errors; if they didn't (and instead return some "default" text), then the danger is that a subclass wouldn't properly override them. I don't know if there's a better way to do this in Python, but I'm open to suggestions. > WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:553 > + output1 = fh1.read() > This doesn't look like it would actually run. Is it tested? > > WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:555 > + output2 = fh2.read() > This either. Same typo. > Good catch. I'm not sure why this didn't fall over, but it may not be covered by unit tests (the test coverage on this file is really poor). I'll fix the typos, but I don't want to add more tests for this file specifically as part of this patch, to avoid confusing things (I will be adding more unit tests for this soon). > WebKitTools/Scripts/webkitpy/layout_tests/test_types/test_type_base_unittest.py:45 > + if __name__ == '__main__': > I think PEP8 says 2 blank lines between global blocks. > Right. Not sure how I missed this in check-webkit-style. > WebKitTools/Scripts/webkitpy/layout_tests/test_types/text_diff.py:71 > + if os.path.exists(filename): > This is redundant. Just remove the indent. True. Will do.
Dirk Pranke
Comment 5 2010-08-24 15:53:06 PDT
(In reply to comment #4) > > WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:553 > > + output1 = fh1.read() > > This doesn't look like it would actually run. Is it tested? > > > > WebKitTools/Scripts/webkitpy/layout_tests/rebaseline_chromium_webkit_tests.py:555 > > + output2 = fh2.read() > > This either. Same typo. > > > > Good catch. I'm not sure why this didn't fall over, but it may not be covered by unit tests (the test coverage on this file is really poor). I'll fix the typos, but I don't want to add more tests for this file specifically as part of this patch, to avoid confusing things (I will be adding more unit tests for this soon). Actually I seem to have had writing a unit test for this particular change on my to-do list but lost track of it. It should be easy to add by itself, so I'll add it.
Dirk Pranke
Comment 6 2010-08-24 16:07:24 PDT
Dirk Pranke
Comment 7 2010-08-24 17:10:46 PDT
Note You need to log in before you can comment on or make changes to this bug.