| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:18185
TEST=None
Review URL: http://codereview.chromium.org/7745007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98517 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
a symlink of the same name inside the directory, which is impossible on the
Chrome OS read-only filesystem
Review URL: http://codereview.chromium.org/7628007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96514 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds autotest control files and an associated pyauto suite
for running the tests in perf.py as an autotest. This change only
allows execution as an autotest, but does not enable the tests to run
continuously in the autotest lab. That will be done in a later CL.
I also modified perf.py so that the v8 benchmark test only runs for a
single iteration, and for the other tests, the number of iterations
can optionally be tweaked by setting an environment variable (useful when
running the perf tests manually).
BUG=chromium-os:18187,chromium-os:18185,chromium-os:18458
TEST=None
Review URL: http://codereview.chromium.org/7617014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96461 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/7481017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93765 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is now possible to pass '-a cont_suite' to autoserv to run continuous instead
of full suite.
BUG=
TEST=
Review URL: http://codereview.chromium.org/7346039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92601 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
run_remote_tests.sh. These tests can only be run around oyster bay.
BUG=None
TEST=run_remote_test.sh desktopui_PyAutoNetworkTests
Review URL: http://codereview.chromium.org/7193021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@89705 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:16282
TEST=This is a test. Run the autotest suite desktopui_PyAutoLoginTests.
Review URL: http://codereview.chromium.org/7134006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@88269 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
in. Currently, there is flakiness in the Login() hook because the new user pod might not be ready or selected yet. This change should fix that.
BUG=chromium-os:15582
TEST=./run_remote_tests.sh desktopui_PyAutoLoginTests
Review URL: http://codereview.chromium.org/7020039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@88012 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PyAuto login automation is broken such that it crashes the browser in cases where the ownership is not taken and you don't wait long enough for chrome to startup, login dialog to show, etc. It takes time for chrome to sink these in.
For this reason pyauto tests on autotest lab machines were failing (the autotest lab machines begin with a clean stateful partition, and then we trigger a session_manager restart after creating enable_chromium_minidumps file)
This CL fixes the launcher.
The Login() automation still needs to be fixed to be resilient to the login dialog to show up.
BUG=15582
TEST=pyauto test fire up on chromeos autotest lab machines
Review URL: http://codereview.chromium.org/7065016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86493 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/7039029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85819 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is so that testserver.log file (create by testserver) can be created.
R=dtu@chromium.org
BUG=
TEST=
Review URL: http://codereview.chromium.org/6988001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84705 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:12641
R=dtu@chromium.org
TEST=
Review URL: http://codereview.chromium.org/6928043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84347 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
s/python/suid-python/ so that we don't end unintentionally using suid python.
BUG=
TEST=
Review URL: http://codereview.chromium.org/6910031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83973 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bidi checker test was using a bad path to locate the js file, fixed that to always find it relative to src root (there is a corresponding CL on Chromium OS to fix the e-build to copy the js over to the test deps).
The plugin test was failing for two reasons, one the plugin not being available (again, corresponding CL on chromium-os tracker to fix that in the e-build), second is Chrome being symlinked. I am not completely sure why this breaks this test, but the executable being in the same directory as the rest of the test files is a more accurate test environment anyway, hence copying it instead of symlinking.
R=zelidrag@chromium.org
BUG=chromium-os:13857
TEST=Ran the full browsertest suite, all passed
Review URL: http://codereview.chromium.org/6904073
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83513 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:14412
TEST=crash_reporter should run and pass on Autotest dashboard after this change.
Review URL: http://codereview.chromium.org/6893010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83210 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you don't tear down the fake DNS server, you hose internet on the bot.
This was leading to failure in a few pyauto tests that run after browser tests.
BUG=chromium-os:14039
TEST=pyauto tests go green
Review URL: http://codereview.chromium.org/6836007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81349 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Several browser tests on Chrome OS fail when run while not logged in. Running tests as a logged in user is also a closer representation of a real testing scenario.
R=nirnimesh@chromium.org
BUG=cros:13857
TEST=Ran the browser tests on a cr-48. The default user logged in and tests passed.
Review URL: http://codereview.chromium.org/6693104
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80711 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing chrome_test dependence is large (about 350MB on ARM). This new
PyAuto dependency caters for cases where this functionality is needed within
Chrome OS without all the rest of the Chrome tests. It is about 30MB.
BUG=chromium-os:13288
TEST=manually copy files into autotest directory, check that run_remote_tests
picks these up and that they operate correctly on a Seaboard with a trivial
PyAuto test (see http://codereview.chromium.org/6766006/)
This will ultimately be installed in the chroot by the chromeos-chrome ebuild.
Review URL: http://codereview.chromium.org/6689027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80395 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Many of the browser tests will not run without this symlink.
BUG=chromium-os:8544
TEST=Run desktopui_BrowserTest.control and see that tests no longer error out complaining they cant find resources.pak
Review URL: http://codereview.chromium.org/6670007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77709 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This should enable about 150 pyauto tests on chromeos.
Get rid of PRIMARY_CHROME suite. Primary chrome is going to be the only
supported way of controlling chromeos-chrome from pyauto anyway.
I've broken down general category failures into their respective bugs, but
there are some that I've not triaged yet. I've bunched them together in one
category at the end.
BUG=chromium-os:12653
TEST=run_remote_tests.sh --remote=[REMOTE] desktopui_PyAutoFunctionalTests
Review URL: http://codereview.chromium.org/6588106
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76626 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pyauto-based chrome tests on ChromeOS.
This CL includes:
- enable_testing.py -- sends dbus call to session_manager to enable testing interface
- pyauto.py -- integration of named automation interface with PyAuto
- desktopui_PyAutoFunctionalTests.py -- setup to use named automation interface. Uses a suid-root binary (as discussed with cmasone) to dbus mesg to session_manager
- PYAUTO_TESTS -- a new suite called "PRIMARY_CHROME" which currently consists of a basic hello world test that controls the primary chrome
- chromeos_basic.py -- a basic test
All plumbing necessary to integrate the named automation interface with autotest and pyauto is included.
It's designed such that it's easy to work directly on a chromeos device while adding/editing a pyauto test, without having to run via autotest every time. Also, the existing pyauto tests (about 200 of them) will begin controlling the primary chrome.
Can be run with run_remote_tests.sh as:
$ ./run_remote_tests.sh --remote <IP> desktopui_PyAutoFunctionalTests
BUG=
TEST=
Review URL: http://codereview.chromium.org/6410134
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@75797 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the past, the sync integration tests used to require a password file
stored on every test device in order to do a gaia sign in using
production gaia servers. This caused the tests to be brittle.
As of today, the sync integration tests no longer rely on a password
file, with gaia sign in being stubbed out locally.
This patch reconfigures the tests on autotest, so that it no longer
looks for a local password file.
In addition, the tests run much faster now, and therefore, we reduce the
max timeout to a more reasonable 2 minutes (in the extreme case).
BUG=chromium-os:11294, chromium-os:9262
TEST=sync_integration_tests
Review URL: http://codereview.chromium.org/6387004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@72561 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/6289005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71809 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:10485
TEST=Run desktopui_PyAutoFunctionalTests.py
Review URL: http://codereview.chromium.org/6030004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69784 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/5560011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68622 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some deps in the chrome tree and support classes on the Chrome OS side
have changed, so update our autotest wrappers to work again. The new
code also takes advantage of some new features in the ChromeTestBase class.
I've also split the control files to each run 1/4 of the browser tests and ui tests. I tried to come up with a way to divide them more cleanly, but this seems the best way to split them across multiple VMs with the infrastructure on the bots. If we used autoserv to run smoke suite, we could be more clever here, but that's a big hammer for this problem.
BUG=chromium-os:8544
TEST=install chrome with tests, then run desktopui_BrowserTest and friends. They should be able to run, though not necessarily succeed.
Review URL: http://codereview.chromium.org/4698004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66168 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This follows the pattern used by other chrome ui tests (desktopui_UITest, desktopui_BrowserTests).
Tests are run as user chronos (not as root) and drive chrome with a clean profile dir per test.
BUG=crosbug.com/4938, crosbug.com/1504
TEST=sh run_remote_tests.sh --remote=<remote> desktopui_PyAutoFunctionalTests
Review URL: http://codereview.chromium.org/3412026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60239 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
class.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/3408006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59590 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/3257006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58029 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
TBR=zbehan
BUG=none
TEST=none
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57746 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
TBR=zbehan
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/3156052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57618 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
avoid circular dependencies on autotest repo in chromeos builds.
TEST=make sure chrome tests still run in autotest framework on chromeos
BUG=none
Review URL: http://codereview.chromium.org/3185029
TBR=zelidrag@chromium.org
Review URL: http://codereview.chromium.org/3169051
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57560 0039d316-1c4b-4281-b951-d872f2087c98
|
|
dependencies on autotest repo in chromeos builds.
TEST=make sure chrome tests still run in autotest framework on chromeos
BUG=none
Review URL: http://codereview.chromium.org/3185029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57556 0039d316-1c4b-4281-b951-d872f2087c98
|