New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 650374 link

Starred by 0 users
Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
█ scunning...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Write policy_AllowOutdatedPlugins test using EP Framework

Project Member Reported by scunning...@chromium.org, Sep 26 2016 
Write automated test for AllowOutdatedPlugins policy using EP Framework.

Comment 1 by scunning...@chromium.org, Sep 28 2016

Labels: -Pri-2 Pri-3
Lowered priority since to NPAPI plugins are no longer supported. UMA Stats show  very low usage.

Comment 2 by scunning...@chromium.org, Sep 30 2016

Cc: scunning...@chromium.org
Owner: ----
Status: Available (was: Assigned)

Comment 3 by pastarmovj@chromium.org, Oct 4 2016 

I might have missed something but what is the EP framework? This will help me reassign this bug to the right owner. Although keep in mind that this policy will soon be obsoleted.

Comment 4 by scunning...@chromium.org, Oct 4 2016 

EP Framework simplifies writing of AutoTest tests of Chrome OS Enterprise policies. The framework is defined in enterprise_policy_base.py. It allows user policies to be downloaded to an un-enrolled device running a test image. Here's an overview: go/cros-epcat-prez

Comment 5 by atwilson@chromium.org, Oct 21 2016

Status: WontFix (was: Available)
This policy is going away in M56 so not going to ever write a test for this.
►

Sign in to add a comment