Tell the testing-framework that we started the tests.

Tell the testing-framework that we started the tests.

Committed: https://code.google.com/p/dart/source/detail?r=956

[floitsch, 2011-10-31 16:53:19]

I'm not 100% sure the nested timeout is necessary, but it can't hurt, and I
prefer this to flaky tests.

[ngeoffray, 2011-10-31 16:55:54]

LGTM, but I can't really say about the nested timeout. Maybe Vijay or Anton will
have an answer.

http://codereview.chromium.org/8430005/diff/4/tools/testing/architecture.py
File tools/testing/architecture.py (right):

http://codereview.chromium.org/8430005/diff/4/tools/testing/architecture.py#n...
tools/testing/architecture.py:78: wait() {
waitForDone?

[floitsch, 2011-10-31 16:59:48]

http://codereview.chromium.org/8430005/diff/4/tools/testing/architecture.py
File tools/testing/architecture.py (right):

http://codereview.chromium.org/8430005/diff/4/tools/testing/architecture.py#n...
tools/testing/architecture.py:78: wait() {
On 2011/10/31 16:55:54, ngeoffray wrote:
> waitForDone?

Done.

[vsm, 2011-10-31 17:48:21]

http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.py
File tools/testing/architecture.py (right):

http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.p...
tools/testing/architecture.py:42: <script type="%(script_type)s"
src="%(source_script)s"></script>
Note, we're changing Dart scripts to execute on DOMContentLoaded (- Anton had a
change that went in this morning).  I'm not sure we guarantee ordering between
the above script execution and the below as written.

[floitsch, 2011-10-31 18:00:36]

http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.py
File tools/testing/architecture.py (right):

http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.p...
tools/testing/architecture.py:42: <script type="%(script_type)s"
src="%(source_script)s"></script>
On 2011/10/31 17:48:21, vsm wrote:
> Note, we're changing Dart scripts to execute on DOMContentLoaded (- Anton had
a
> change that went in this morning).  I'm not sure we guarantee ordering between
> the above script execution and the below as written. 

But that would mean that the JS script is executed even earlier. Do you mean
that I should increase the first timeout?

[Anton Muhin, 2011-10-31 18:19:24]

http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.py
File tools/testing/architecture.py (right):

http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.p...
tools/testing/architecture.py:51: // A window.postMessage might have been
enqueued after this timeout.
I don't know all the details, but maybe trigger first callback on
DOMContentLoaded?

[floitsch, 2011-10-31 18:48:45]

On 2011/10/31 18:19:24, antonmuhin wrote:
> http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.py
> File tools/testing/architecture.py (right):
> 
>
http://codereview.chromium.org/8430005/diff/4004/tools/testing/architecture.p...
> tools/testing/architecture.py:51: // A window.postMessage might have been
> enqueued after this timeout.
> I don't know all the details, but maybe trigger first callback on
> DOMContentLoaded?

http://codereview.chromium.org/8427012/