| 9fef4639415a0481373e073f40b7c32ed93a99b5 |
|
11-Jun-2014 |
Chris Masone <cmasone@chromium.org> |
Stop the UI instead of stopping the session in some tests.
Some tests need to unmount and remove a cryptohome at the end of the test.
Stopping the user's session and then unmounting the user's cryptohome
can cause a race with ui.conf's session cleanup code (which ALSO wants to
own unmounting the user's cryptohome). Find the tests that were manually
unmounting during cleanup and make them stop or restart the UI instead.
BUG=chromium:381034
TEST=run these three tests.
Change-Id: I2fae64fdfea8da569e5ab61691fddbe3d1157708
Reviewed-on: https://chromium-review.googlesource.com/203320
Reviewed-by: Darren Krahn <dkrahn@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 64170f8e7053f92f4bbad501c61a352fdabf6d82 |
|
14-Mar-2014 |
Chris Masone <cmasone@chromium.org> |
Update all login_* tests to use CryptohomeProxy
Instead of shelling out to a command-line tool, we should
talk to crypthomed directly over DBus.
BUG=chromium:344862
TEST=login_*
Change-Id: I3a57d8158638cab60e8a7e0dd5c72293e87a87ac
Reviewed-on: https://chromium-review.googlesource.com/190343
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| a2b32851e8716f188dde273c73f4c76058bbd289 |
|
26-Feb-2014 |
Chris Masone <cmasone@chromium.org> |
Ensure that ui is stopped when monkeying with owner policy/key
The session_manager keeps copies of the owner key and policy in memory
and writes them to disk when it shuts down. This means that messing with them
while the UI is up will not persist across a UI restart. At least one test
was making this mistake (login_OwnershipTaken) leading to test-ordering
effects. This change updates ownership.py to correctly enforce this invariant.
BUG=chromium:338528
TEST=run login_*Ownership*
Change-Id: I72bb20b23abf3837e14b21cc6689cc383847b5db
Reviewed-on: https://chromium-review.googlesource.com/188077
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Mattias Nissler <mnissler@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 63abfd2ad9eecdea50ca2567a6324370ede77d58 |
|
31-Oct-2013 |
Chris Masone <cmasone@chromium.org> |
Use real, empty policy in RemoteOwnership test
I'd been using a dummy string for the policy payload in this test,
which causes other processes on the system to gripe that they can't
parse the system's device policy. To remove these potential red-
herrings from the test logs, just use an actual empty PolicyData.
BUG=None
TEST=run login_RemoteOwnership
Change-Id: I546d5e22e7cb49d0f02776b8765fe940eb39014c
Reviewed-on: https://chromium-review.googlesource.com/175282
Commit-Queue: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 6cb26ad178990814fce3209c464afe7f131ec5b0 |
|
21-May-2013 |
Elly Fong-Jones <ellyjones@chromium.org> |
[autotest] remove dependencies on /home/chronos/user
BUG=chromium:212419
TEST=suite_Smoke
Change-Id: I8849e3eb6e76a3a3358422f1c2269a926d35994f
Signed-off-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56050
Reviewed-by: Will Drewry <wad@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 5d010aa50a0694d498e8317fd8044e56474ce7ed |
|
06-May-2013 |
Chris Masone <cmasone@chromium.org> |
Add multiprofile tests for session_manager.StartSession()
Multiple calls to StartSession() with different users should be allowed,
while multiple calls with the same user should not.
BUG=chromium:235179
TEST=run these new tests
CQ-DEPEND=I1200c4463d43cd8cf7d49a2f9f0667ac1cccc261
CQ-DEPEND=I5ee9fb18e1f8c1a933b899acc62618323f2df9bf
Change-Id: I912d3ded053a7f0f41c604f5ffef15477d634017
Reviewed-on: https://gerrit.chromium.org/gerrit/50223
Commit-Queue: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| d976e0ed3cb28e532f15826c5071149b8fabeaf8 |
|
06-May-2013 |
Chris Masone <cmasone@chromium.org> |
Move ownership tests to use composition instead of inheritance
Using composition like this makes it clearer what each test is doing, instead
of having stuff happen in the base class as if by magic.
BUG=chromium:222778
TEST=login_*Ownership*
STATUS=Fixed
Change-Id: I7dbb71e1a712efacfdbe7ad64f4ef74ea0793919
Reviewed-on: https://gerrit.chromium.org/gerrit/50194
Commit-Queue: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 4dbb67c9f8fbb9d31cffa910feda5186c4c1994a |
|
01-May-2013 |
Chris Masone <cmasone@chromium.org> |
Update ownership tests infrastructure to handle multiprofile
This doesn't add any tests for multiprofile use cases, but makes sure that
the test infrastructure will be able to handle such tests.
BUG=chromium:221770
TEST=login_RemoteOwnership login_OwnershipApi login_OwnershipTaken login_OwnershipRetaken login_OwnershipNotRetaken login_UserPolicyKeys
Change-Id: Ieba74ff9ee3b4b6f79dca70d71c10eed3e5c2239
Reviewed-on: https://gerrit.chromium.org/gerrit/49723
Commit-Queue: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 67f77a12725f81b88235a9d865bd4b8322fb83c7 |
|
21-Oct-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Move to restarting the UI using upstart, by default
The contract between Chrome and the session manager wrt signing out is
changing, again. As such, we're going to make StopSession either
behave differently or go away. So, to restart the UI during a test,
let's just use the upstart 'restart ui' command.
BUG=chromium-os:21877
TEST=suite_Smoke and login_*Ownership*
STATUS=Verified
Change-Id: Ib1afb0dfe5bd7276df9220b61df2c6a4a4661e86
Reviewed-on: http://gerrit.chromium.org/gerrit/10512
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| d51ac9cdab93aee5b408dde4543a00d9913f740f |
|
10-Sep-2011 |
David James <davidjames@chromium.org> |
Refactor tests to consistently wait for login prompt to show up after logout.
This CL refactors the autotest suite to consistently check for the login prompt
visibility whenever the session manager is killed. This ensures that the Window
Manager can depend on being fully initialized prior to being killed.
BUG=chromium-os:18919
TEST=Ran trybot run with VM tests.
Change-Id: I1747bc55c66c3eeae10e2cafa2dfc8219d758874
Reviewed-on: http://gerrit.chromium.org/gerrit/8184
Commit-Ready: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 105706efb7ebc97575dafd7a92bb815f79d8bb47 |
|
29-Apr-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] Add test for the re-taking of ownership after the owner key is lost
BUG=chromium-os:11193
TEST=run this test
Change-Id: I95b402d47ec430a8556d012d9a2ee2614507a1e4
Review URL: http://codereview.chromium.org/6880288
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| 14b746590380faa30a2119b3be1d5fcf2d953f11 |
|
23-Apr-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] More coverage of ownership API
Make login_OwnershipApi not need to generate owner keys, so that it can be
included in suite_Smoke and the BVT. Also clean up a bit of logging around
ownership test infrastructure.
BUG=chromium-os:14443
TEST=suite_Smoke
Change-Id: I13e57f84753e0c14d987cafa6f52574742bc4fe9
R=sosa@chromium.org
Review URL: http://codereview.chromium.org/6880156
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|
| eac4f4f0839c57d84d5c042deed64cf6d2189d26 |
|
06-Apr-2011 |
Chris Masone <cmasone@chromium.org> |
[autotest] More ownership/device policy tests
Improve ownership test infrastructure, make a base class for ownership tests
that actually exercise the API, and add a new test that validates the owner
key setting/rotating logic that will be (mostly) used by enterprise managed
device support.
BUG=13746
TEST=login_Ownership*, login_RemoteOwnership
Change-Id: I6a3a405744ca585bb93bb7b0a47f4536b0832744
R=sosa@chromium.org
Review URL: http://codereview.chromium.org/6677180
/external/autotest/client/site_tests/login_RemoteOwnership/login_RemoteOwnership.py
|