New issue
Advanced search Search tips

Issue 628744 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Write policy_PinnedLauncherApps test using EP Framework

Project Member Reported by scunning...@chromium.org, Jul 15 2016

Issue description

Write an automated test of the PinnedLauncherApps user policy, using the AutoTest+Telemetry Enterprise Policy Test framework. This policy is a JSON list, and is dependent on whether or not the pinned app is installed. Test will use ExtensionSettings user policy to force-install certain test apps, though it will not thoroughly test the ExtensionSettings policy.

In general, the possible policy values are:
- NotSet: Default pinning is used at first. User can fully manage pinning of apps to the Shelf: Pin, Move, UnPin.
- [app_id1, app_id2, ...]: The listed apps, if installed for user, are pinned to the Shelf in the order listed.  If a default app is not listed (e.g., chrome, gmail), it will be unpinned from the Shelf.

Note: This test will not verify the UI behavior introduced in  issue 549083 : Pinned apps shadow user pinned apps. User can move/unpin user-added apps, but cannot pin new apps, or move/unpin policy-pinned apps. Those behaviors are thoroughly covered by unittests.
 
Status: WontFix (was: Assigned)
CL https://codereview.chromium.org/2055553004 added sufficient unittests and browsertests needed to deprecate manual testing. No AutoTest needed.
Owner: ----

Sign in to add a comment