Hi,
So can we run unit tests without any port as in
Tools/TestWebKitAPI
When I tried to build it is breaking and when I checked it is looking for
Apple macros to build.
Build script I picked from Tools/Script/build-api-tests.
Thanks,
Nags
On 29 Jun 2017 9:23 p.m., "Konstantin Tokarev" wrote:
Hi,
So can we run unit tests without any port as in
Tools/TestWebKitAPI
When I tried to build it is breaking and when I checked in build script it
is looking for Apple macros to build.
Build script I picked from Tools/Script/build-api-tests.
Thanks,
Nagendra
On 29 Jun 2017 9:23 p.m., "Konstanti
29.06.2017, 18:46, "Nagendra K" :My port is not ready yet as we decide to port module by module once we cross compile base webit on device. So is possible to test the WebKit built without the port, at least some tests without any UI.You can run some tests manually, by opening their html files in
My port is not ready yet as we decide to port module by module once we
cross compile base webit on device. So is possible to test the WebKit built
without the port, at least some tests without any UI.
Thanks,
Nagendra
On 29 Jun 2017 8:50 p.m., "Konstantin Tokarev" wrote:
>
>
> 29.06.2017, 18:18
29.06.2017, 18:18, "Nagendra K" :
> Hi,
>
> I have a requirement to check if a particular WebKit or latest WebKit works
> on the embedded platform. They have custom port which is complex, so plan to
> build the new WebKit as a separate process to check build works fine and then
> bring their c
Hi,
I have a requirement to check if a particular WebKit or latest WebKit works
on the embedded platform. They have custom port which is complex, so plan
to build the new WebKit as a separate process to check build works fine and
then bring their changes later. Once we build WebKit I want to check
On Wed, Oct 21, 2009 at 2:17 AM, Shinichiro Hamaji wrote:
>
> - fast/forms/basic-textareas-quirks
> author: ojan
> trac: http://trac.webkit.org/changeset/41792
>
Doh. The quirks version of this test was rolled into the
basic-textareas.html test before checking in. I'll remove the extra
expectation
On Oct 21, 2009, at 2:17 AM, Shinichiro Hamaji wrote:
However, there are some cases in which people forgot to add test
files.
Thanks for tackling this!
- fast/dynamic/8952-reduction
author: darin
trac: http://trac.webkit.org/changeset/15459
comment: now the png file is in platform/mac
In
Hi WebKit,
I found there are several expectation files which don't have
corresponding tests. Most of them are fine. People just forgot to remove
expectation files when they removed the tests. However, there are some
cases in which people forgot to add test files. For such cases, I
think we should
I wonder if it makes sense to put this in a part of svn.webkit.org
that isn't pulled into the default checkout. People who care about
the chromium expectations could then map it into their client
perforce-style using something like the DEPS system.
What's the plan for mapping V8 into the build sy
One of the steps in completing the Chromium WebKit port is moving
layout test baselines from Chromium repository to svn.webkit.org
(https://bugs.webkit.org/show_bug.cgi?id=28397). This is a pretty
heavy chunk: over 20K files, weighing about 260MB. In comparison, this
is more than the current conten
on 12.12.2007 22:22, Rui Jiang at [EMAIL PROTECTED] wrote:
> Pardon me for this newbie problem. I just followed instructions on
> webkit.org, got a clean svn checkout yesterday, did a build and all
> successful. However, when I ran the layout test, they all failed.
>
> I could run safari, it work
Hi all,
Pardon me for this newbie problem. I just followed instructions on
webkit.org, got a clean svn checkout yesterday, did a build and all
successful. However, when I ran the layout test, they all failed.
I could run safari, it works mostly when browsing webpages, however,
whenever I typ
13 matches
Mail list logo
