Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(12)

Issue 195106: Implement per-test timeout for UI tests. (Closed)

Created:
11 years, 3 months ago by Paweł Hajdan Jr.
Modified:
9 years, 7 months ago
CC:
chromium-reviews_googlegroups.com
Visibility:
Public.

Description

Implement per-test timeout for UI tests. Doing it on the browser side makes things simpler - we don't have to deal with preempting sync IPC messages and things like that. It's possible that this will hit other problems, but seems like a good start. TEST=none BUG=22054

Patch Set 1 #

Total comments: 1

Patch Set 2 : add command line flag #

Total comments: 1

Patch Set 3 : initialize the variable #

Patch Set 4 : sync with trunk #

Unified diffs Side-by-side diffs Delta from patch set Stats (+36 lines, -1 line) Patch
M chrome/browser/automation/automation_provider.h View 1 2 3 1 chunk +2 lines, -0 lines 0 comments Download
M chrome/browser/automation/automation_provider.cc View 1 2 3 2 chunks +7 lines, -0 lines 0 comments Download
M chrome/test/automation/automation_messages_internal.h View 1 2 3 1 chunk +4 lines, -0 lines 0 comments Download
M chrome/test/automation/automation_proxy.h View 1 chunk +2 lines, -0 lines 0 comments Download
M chrome/test/automation/automation_proxy.cc View 1 chunk +4 lines, -0 lines 0 comments Download
M chrome/test/ui/ui_test.h View 1 chunk +1 line, -0 lines 0 comments Download
M chrome/test/ui/ui_test.cc View 1 2 3 5 chunks +16 lines, -1 line 0 comments Download

Messages

Total messages: 9 (0 generated)
Paweł Hajdan Jr.
11 years, 3 months ago (2009-09-16 21:31:53 UTC) #1
huanr
What is the benefit of setting per test timeout? http://codereview.chromium.org/195106/diff/1/7 File chrome/test/ui/ui_test.cc (right): http://codereview.chromium.org/195106/diff/1/7#newcode48 Line ...
11 years, 3 months ago (2009-09-16 21:58:47 UTC) #2
Paweł Hajdan Jr.
On 2009/09/16 21:58:47, huanr wrote: > What is the benefit of setting per test timeout? ...
11 years, 3 months ago (2009-09-17 19:15:33 UTC) #3
huanr
http://codereview.chromium.org/195106/diff/3002/3008 File chrome/test/ui/ui_test.cc (right): http://codereview.chromium.org/195106/diff/3002/3008#newcode112 Line 112: terminate_timeout_ms_(kWaitForTerminateMsec) { set per_test_timeout default.
11 years, 3 months ago (2009-09-17 19:48:20 UTC) #4
Paweł Hajdan Jr.
Could you explain the comment? I'm not sure what to do... On Thu, Sep 17, ...
11 years, 3 months ago (2009-09-17 19:50:08 UTC) #5
Paweł Hajdan Jr.
Should be fixed. Please take a look.
11 years, 3 months ago (2009-09-18 17:33:13 UTC) #6
huanr
LGTM
11 years, 3 months ago (2009-09-18 17:34:45 UTC) #7
jcampan
> It would be nice to have a more general timeout, for all UI tests. ...
11 years, 1 month ago (2009-11-04 17:42:30 UTC) #8
Paweł Hajdan Jr.
11 years, 1 month ago (2009-11-04 17:47:59 UTC) #9
On Wed, Nov 4, 2009 at 18:42, Jay Campan <jcampan@chromium.org> wrote:

> > It would be nice to have a more general timeout, for all UI tests. I have
> a
> > patch ready at http://codereview.chromium.org/195106, but landing it is
> > complicated (nsylvain and huanr can explain it).
> ViewEventTest are not UI tests, they are unit-tests (run in-process)
> that do UI magic.
>

I see. Please ignore my earlier comment then.

Powered by Google App Engine
This is Rietveld 408576698