I'm going to reassign this to phajdan.jr@ as per our recent discussions ...

I also don't think this is actually blocked on the CIPD work ( bug 663843 ), unless I've forgotten something; I think it was just that iannucci@ was going to work on 663843 first.

This has nothing to do with luci-config

Yes, it's possible to clean up a lot of it without CIPD.

Infra component is not specific enough and we are supposed to find more specific component during triage. I don't know where it should belong to, adding to Infra>Client>Chrome for now.

I'm not actively working on this ...

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I think this is a good thing to work on. I've been thinking about doing work in this area recently. Things have changed since this bug was originally filed. I took a glance at the doc and it doesn't seem very finished.

You are correct that the doc in the description is relatively unfinished.

A more recent doc, that I'd work on instead, is https://bit.ly/chromium-test-step-api . I'd like to finish that, at least, and we can then see if that plus the other bit.ly "standards" docs make the first one obsolete.

I was thinking about taking a stab at getting the test-step-api doc close to accurate (i.e., reflect the current IsolatedScriptTest API at least) today or tomorrow.