On Oct 26, 2012, at 7:21 PM, Rik Cabanier caban...@gmail.com wrote:
On Fri, Oct 26, 2012 at 9:06 AM, Peter Kasting pkast...@google.com wrote:
On Fri, Oct 26, 2012 at 8:27 AM, Rik Cabanier caban...@gmail.com wrote:
It is valid for a const method to return you a new object ie a const
On Oct 26, 2012, at 11:11 PM, Ryosuke Niwa rn...@webkit.org wrote:
I’m sure Antti, Alexey, and others who have worked on the loader and other
parts of WebKit are happy to write those tests or list the kind of things
they want to test. Heck, I don’t mind writing those tests if someone
We could clear the cache between tests but run each test twice in a row.
Second run will then happen with deterministically pre-populated cache.
That would both make things more predictable and improve our test coverage
for cached cases. Unfortunately it would also slow down testing
significantly,
We can live in one of two worlds:
1) LayoutTests that concern themselves with specific network/loading
concerns need to use unique URLs to refer to static data; or
2) DRT clears JS-visible state between tests.
The pros/cons seem clear to me:
Pro#1: loading/caching code is coincidentally
On Sun, Oct 28, 2012 at 6:12 AM, Maciej Stachowiak m...@apple.com wrote:
I am not sure a blanket rule is correct. If the Foo* is logically related
to the object with the foo() method and effectively would give access to
mutable internal state, then what you say is definitely correct. But if
On Oct 26, 2012, at 11:11 PM, Ryosuke Niwa rn...@webkit.org wrote:
I’m sure Antti, Alexey, and others who have worked on the loader and other
parts of WebKit are happy to write those tests or list the kind of things
they want to test. Heck, I don’t mind writing those tests if someone could
It is useful to say that getting a pointer to T from an object of type S does
not change S's state.
-F
On Oct 28, 2012, at 2:09 PM, Peter Kasting pkast...@chromium.org wrote:
On Sun, Oct 28, 2012 at 6:12 AM, Maciej Stachowiak m...@apple.com wrote:
I am not sure a blanket rule is correct.
On 10/28/2012 08:25 PM, Ami Fischman wrote:
We can live in one of two worlds:
1) LayoutTests that concern themselves with specific
network/loading concerns need to use unique URLs to refer to
static data; or
2) DRT clears JS-visible state between tests.
The pros/cons
Hi webkit-dev,
When I include fprintf(stderr, ...) statements in WebKit code that I expect
to be executed when running a set of layout tests, the summary page of
run-webkit-tests will sometimes only show a subset of these statements.
However, when I add a CRASH() somewhere in the code, the
On Sun, Oct 28, 2012 at 2:47 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Oct 28, 2012 at 2:09 PM, Dirk Pranke dpra...@chromium.org wrote:
On Oct 26, 2012, at 11:11 PM, Ryosuke Niwa rn...@webkit.org wrote:
I’m sure Antti, Alexey, and others who have worked on the loader and
other parts
On 10/29/2012 12:29 AM, Terry Anderson wrote:
Hi webkit-dev,
When I include fprintf(stderr, ...) statements in WebKit code that I
expect to be executed when running a set of layout tests, the summary
page of run-webkit-tests will sometimes only show a subset of these
statements. However,
On Sun, Oct 28, 2012 at 4:37 PM, Dirk Pranke dpra...@chromium.org wrote:
On Sun, Oct 28, 2012 at 2:47 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Oct 28, 2012 at 2:09 PM, Dirk Pranke dpra...@chromium.org
wrote:
On Oct 26, 2012, at 11:11 PM, Ryosuke Niwa rn...@webkit.org wrote:
12 matches
Mail list logo
