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

Issue 781102 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

factory: test default UI should provide parameters during execution

Project Member Reported by hungte@chromium.org, Nov 3 2017

Issue description

Currently the test default UI (for non-interactive tests like stressapptest) we can see the test parameters, but it's not evaluated yet. This is not convenient when debugging that we do want to quickly find out "what's the param in current stage", especially we have more eval-type params today in JSON test list.

I think we may want:
 - In goofy invocation, when the args were solved, make a copy to the invocation
 - test default UI should show both evaluated values AND original value (the eval string)
 - If possible, also provide a way so we can inspect params even if the test has its own UI, for example adding a button in additional to "mark failed", or a popup menu item.
 
Status: WontFix (was: Untriaged)
ok... just realized I can use the View Logs to find evaluated params.

So maybe this issue can be WONTFIX.

Sign in to add a comment