Hi,
In src/chrome/test/automation, it has a automation_proxy_uitest.cc, How can
I run the automation test on MacOSX?
I see that is a directory
xcodebuild/chrome.build/Debug/automated_ui_tests.build, but there is no
*.app under there.
Thank you for any tip.
Most (all?) of the uitests are compiled into an executable called uitests. Use
xcodebuild/Debug/ui_tests --gtest_print_time
to list all test names, then do
xcodebuild/Debug/ui_tests --gtest_filter=SavePageTest.SaveHTMLOnly
to execute the test you want.
ps: First hit when searching
I don't know. But I'm sure a search engine of your choice can help you here :-)
The steps should be somewhere along the lines of open
chrome.xcodeproj, select 'run ui_tests' in the overview dropdown, edit
project settings to add a command-line param, hit debug. I'm sure
you'll figure it out.
On
Right now our plugin loading code matches Firefox in the search path order.
1 $MOZ_PLUGIN_PATH
2 ~/.mozilla/plugins
3 path_to_chrome_binary/plugins - analogous to Firefox
4 /usr/lib/mozilla/plugins and related directories - what Firefox uses
On systems that have nspluginwrapper installed,
Can't we blacklist nspluginwrapper, and use the same logic that it uses to
find the real plugins?
On Fri, Aug 28, 2009 at 11:01 AM, Evan Martin e...@chromium.org wrote:
Right now our plugin loading code matches Firefox in the search path order.
1 $MOZ_PLUGIN_PATH
2 ~/.mozilla/plugins
3
On Fri, Aug 28, 2009 at 11:03 AM, John Abd-El-Malekj...@chromium.org wrote:
Can't we blacklist nspluginwrapper, and use the same logic that it uses to
find the real plugins?
I have been thinking about this. The tricky part is that for *some*
plugins, nspluginwrapper is the best we currently
Thank you. I ran the Automation UI test by ./ui_tests
--gtest_filter=Automation*
Can you please tell me how can I run it in XCode so that I can debug/step
thru each Test Case?
On Fri, Aug 28, 2009 at 7:20 AM, Nico Weber tha...@chromium.org wrote:
Most (all?) of the uitests are compiled into
On Fri, Aug 28, 2009 at 7:01 PM, Evan Martine...@chromium.org wrote:
Right now our plugin loading code matches Firefox in the search path order.
1 $MOZ_PLUGIN_PATH
2 ~/.mozilla/plugins
3 path_to_chrome_binary/plugins - analogous to Firefox
4 /usr/lib/mozilla/plugins and related
On Fri, Aug 28, 2009 at 11:03 AM, John Abd-El-Malek j...@chromium.orgwrote:
Can't we blacklist nspluginwrapper, and use the same logic that it uses to
find the real plugins?
Last time I looked, the way nspw works: for each wrapped plugin it installs
a version of the nspw plugin into the
Hi all,
Has anyone tried to build the Chromium IPC/shared memory code on 64-bit Mac
OS? We have a need for IPC and shared memory between 64-bit and 32-bit
processes, and what Chrome has seems to be a good fit for our needs. From
my first glance through the code, it looks like standard POSIX
On Fri, Aug 28, 2009 at 3:44 PM, Mark Wangm...@cooliris.com wrote:
Has anyone tried to build the Chromium IPC/shared memory code on 64-bit Mac
OS? We have a need for IPC and shared memory between 64-bit and 32-bit
processes, and what Chrome has seems to be a good fit for our needs. From
my
Hi Mark,
We haven't specifically tested the ipc layer as a method to communicate
between 64 32-bit processes on OS X.
At it's core the IPC layer just consists of a pipe to which we read write
binary data, therefore if the binary representation of the data types that
you want to push over the
The message serialization code, as I recall, had problems in making
the 64-bit port where two types that were previously separate ended up
typedef'ing to the same underlying type. I think Dean removed all of
those to make the 64-bit port work now, but that may have the
consequence that code that
On Thu, Aug 27, 2009 at 23:07, Nico Webertha...@chromium.org wrote:
I accidentally fixed the problem by running something like
rm -rf .git/svn/
git svn fetch;
This one is most likely, the next one being the git pull.
... git merge trunk
git merge refs/remotes/origin/trunk
git
Thanks a lot, Nicolas!
yours,
anton.
On Fri, Aug 28, 2009 at 8:45 AM, Darin Fisherda...@chromium.org wrote:
Thank you!!!
On Thu, Aug 27, 2009 at 4:03 PM, Nicolas Sylvain nsylv...@chromium.org
wrote:
And now it is also running test_shell_tests in purify and valgrind:
15 matches
Mail list logo
