|
|
Created:
4 years ago by Gleb Lanbin Modified:
3 years, 11 months ago CC:
chromium-reviews, ojan+watch_chromium.org, szager+layoutwatch_chromium.org, glebl+reviews_chromium.org, atotic+reviews_chromium.org, blink-reviews-layout_chromium.org, pdr+renderingwatchlist_chromium.org, eae+blinkwatch, leviw+renderwatch, zoltan1, jchaffraix+rendering, blink-reviews, kinuko+watch Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMake NGBlockLayoutAlgorithmTest inherit RenderingTest
With RenderingTest it's possible to separate HTML test representation and unittest validation logic.
BUG=635619
Review-Url: https://codereview.chromium.org/2560233003
Cr-Commit-Position: refs/heads/master@{#444988}
Committed: https://chromium.googlesource.com/chromium/src/+/ff9ccb9534870244065db87766a709a23647ff6f
Patch Set 1 #Patch Set 2 : added an example how to test LayoutNG specific but still use RenderingTest #
Total comments: 1
Patch Set 3 : Make NGBlockLayoutAlgorithmTest inherit RenderingTest #Patch Set 4 : revert ScopedRuntimeEnabledFeatureForTest #Messages
Total messages: 37 (29 generated)
glebl@chromium.org changed reviewers: + ikilpatrick@chromium.org
The CQ bit was checked by glebl@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Convert NGBlockLayoutAlgorithmTest.CollapsingMarginsCase1 to a SimTest. The main benefit of SimTest is that it eliminates the necessity to construct a test case HTML representation manually and makes it read directly from file. BUG=635619 ========== to ========== Convert NGBlockLayoutAlgorithmTest.CollapsingMarginsCase1 to a SimTest. The main benefit of SimTest is that it eliminates the necessity to construct a test case HTML representation manually and makes it read directly from file. BUG=635619 ==========
glebl@chromium.org changed reviewers: + cbiesinger@chromium.org
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by glebl@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
Patchset #1 (id:1) has been deleted
Patchset #1 (id:20001) has been deleted
Description was changed from ========== Convert NGBlockLayoutAlgorithmTest.CollapsingMarginsCase1 to a SimTest. The main benefit of SimTest is that it eliminates the necessity to construct a test case HTML representation manually and makes it read directly from file. BUG=635619 ========== to ========== Make NGBlockLayoutAlgorithmTest inherit RenderingTest With RenderingTest it's possible to separate HTML test representation and unittest validation logic. BUG=635619 ==========
The CQ bit was checked by glebl@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
glebl@chromium.org changed reviewers: + eae@chromium.org
adding eae@ for third_party/WebKit/Source/platform
The main downside of a simtest is that you're not really testing layoutng, you are testing the combination of layoutng with the legacy integration. Do you think that's worth it?
On 2016/12/12 22:13:23, cbiesinger wrote: > The main downside of a simtest is that you're not really testing layoutng, you > are testing the combination of layoutng with the legacy integration. Do you > think that's worth it? update the patch with an examples that tests LayoutNG code but still uses injected HTML layout tree. From my personal experience creating LayoutTree manually is a bit error prone. Also I think we do want to test how LayoutNG interacts with legacy code (e.g. we have "Render google.com in LayoutNG" OKR).
Like Christian said this tests things slightly differently. That's perfectly fine but something to be aware of. Using this still of tests in conjunction with regular unit tests sounds like a good idea to me. It is no replacement however. Does that make sense to both of you? If so, LGTM w/suggestions. https://codereview.chromium.org/2560233003/diff/60001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/layout/ng/test_data/margins_collapse1.html (right): https://codereview.chromium.org/2560233003/diff/60001/third_party/WebKit/Sour... third_party/WebKit/Source/core/layout/ng/test_data/margins_collapse1.html:1: <!DOCTYPE html> Please add a comment explaining how this html file is used and include a pointer to the unit test.
Yes that sounds good to me.
The CQ bit was checked by glebl@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...) android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)
The CQ bit was checked by glebl@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by glebl@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from eae@chromium.org Link to the patchset: https://codereview.chromium.org/2560233003/#ps100001 (title: "revert ScopedRuntimeEnabledFeatureForTest")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 100001, "attempt_start_ts": 1484891031822050, "parent_rev": "8729d0519f3f26c833e6ece958e3fd3c16d1e2b5", "commit_rev": "ff9ccb9534870244065db87766a709a23647ff6f"}
Message was sent while issue was closed.
Description was changed from ========== Make NGBlockLayoutAlgorithmTest inherit RenderingTest With RenderingTest it's possible to separate HTML test representation and unittest validation logic. BUG=635619 ========== to ========== Make NGBlockLayoutAlgorithmTest inherit RenderingTest With RenderingTest it's possible to separate HTML test representation and unittest validation logic. BUG=635619 Review-Url: https://codereview.chromium.org/2560233003 Cr-Commit-Position: refs/heads/master@{#444988} Committed: https://chromium.googlesource.com/chromium/src/+/ff9ccb9534870244065db87766a7... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:100001) as https://chromium.googlesource.com/chromium/src/+/ff9ccb9534870244065db87766a7... |