Test Planning
 1. Does the feature need manual testing?
Yes
 2. Feature implementation status (what is currently working and not working/known issues, all the code landed in canary, ready for testing etc.)
All code landed.
 3. Link to Design Doc: https://docs.google.com/document/d/1Of_-JpwCPY6MGfrJCMbZ6PagRI28gjO277BQ4s7TZb4
 4. Link to Test Plan: (High level test cases, specific setup, flags etc) 
 5. Are there any special points of interest from a testing perspective?
No.
 6. Link to demos (if any): NA
 7. Targeted Platforms.
iOS
 8. Is the work flow same as desktop and Mobile? (Answer if applicable to both Desktop and Mobile)
NA

Automation
 9. What's automated? (Unit tests, API tests, Browser tests)  Please provide links to automated tests.
drop_and_navigate_interaction has a unit test, xctests can't drag outside of the app so there's no egtests.  Perhaps with EG2 this will be possible.
 10. What’s not automated that needs manual testing?
Dragging in links from outside the app
 11. List reasons for still needing manual testing.
Not possible with current frameworks

Feature-Component-Ownership Details
 12. What is the crbug label/component for the feature?
There's no umbrella drag and drop component, it belongs to each component, e.g.
UI>Browser>Omnibox or UI>Browser>TabStrip, 
 13. Are there any other team members or mailing lists that should be notified if issues are found?
cc: jif@chromium.org

Stability
 14. Is there a mechanism to turn off the feature if it breaks product functionality or performance?
Controlled by Finch
 15. List UMA stats and coverage to measure stability, It’s highly recommend always adding Stability.Counts and CrashExitCodes.* to your json
Nothing new, we will monitor crashes and cpm.
 16. What are you finch studies and what % rollout are you requesting for each group.
Roll to 100%
 17. How are you monitoring the stability of the experiment groups.
Crashes, cpm...

Performance:
 18. Any performance impact? Did the feature get tested on perf waterfall?
No.

 
 

Test Planning
 1. Does the feature need manual testing?
Yes
 2. Feature implementation status (what is currently working and not working/known issues, all the code landed in canary, ready for testing etc.)
All code landed.
 3. Link to Design Doc: https://docs.google.com/document/d/1Of_-JpwCPY6MGfrJCMbZ6PagRI28gjO277BQ4s7TZb4
 4. Link to Test Plan: (High level test cases, specific setup, flags etc) 
 5. Are there any special points of interest from a testing perspective?
No.
 6. Link to demos (if any): NA
 7. Targeted Platforms.
iOS
 8. Is the work flow same as desktop and Mobile? (Answer if applicable to both Desktop and Mobile)
NA

Automation
 9. What's automated? (Unit tests, API tests, Browser tests)  Please provide links to automated tests.
drop_and_navigate_interaction has a unit test, xctests can't drag outside of the app so there's no egtests.  Perhaps with EG2 this will be possible.
Some EG test to drag and drop from *within* the app are in the work: https://bugs.chromium.org/p/chromium/issues/detail?id=759112
 10. What’s not automated that needs manual testing?
Dragging in links from outside the app
 11. List reasons for still needing manual testing.
Not possible with current frameworks

Feature-Component-Ownership Details
 12. What is the crbug label/component for the feature?
There's no umbrella drag and drop component, it belongs to each component, e.g.
UI>Browser>Omnibox or UI>Browser>TabStrip, 
 13. Are there any other team members or mailing lists that should be notified if issues are found?
cc: jif@chromium.org

Stability
 14. Is there a mechanism to turn off the feature if it breaks product functionality or performance?
Controlled by Finch
There's also a "Drag and Drop" switch in chrome://flags
 15. List UMA stats and coverage to measure stability, It’s highly recommend always adding Stability.Counts and CrashExitCodes.* to your json
Nothing new, we will monitor crashes and cpm.
 16. What are you finch studies and what % rollout are you requesting for each group.
Roll to 100%
 17. How are you monitoring the stability of the experiment groups.
Crashes, cpm...

Performance:
 18. Any performance impact? Did the feature get tested on perf waterfall?
No.