OE AutoDiscovery Test Plan

The most important scenarios to test are configuring real ISP accounts.  The job isn't done until we can guarantee the user experience is good when users enter any of the top 20 ISP email addresses into the Create Account wizard.

Here are the top ISPs that need to be tested:

There are 5 main scenarios:

• No Settings: If you enter an email address like "JoeUser@ucla.edu", no settings will be returned.  The AutoDiscovery page will time out and the user will go to the Protocol/ServerName page.

• Settings Downloaded: If you enter an email address like "JoeUser@yahoo.com", settings will be returned.  The AutoDiscovery page will take the user to the DisplayName page.

• Use Web Based Mail: If you enter an email address like "JoeUser@aol.com", settings will be returned that tell the user to use a web page to send and receive email.  The AutoDiscovery page will take the user to the UseWebBasedMail page which on Win2k will have hyperlinks to launch the web page.

• See Web Page for Info: If you enter an email address like "JoeUser@webtv.net", settings will be returned that tell the user to go to a web page to find out information about email support.  The AutoDiscovery page will take the user to the ServerInfo page which on Win2k will have hyperlinks to launch the web page.

Contacts:

• Shell Dev: BryanSt (contact first)

• Outlook Express: CSager (PM) and YSt (Dev)

• autodiscovery.windows.com: Operations: Doug Stamper, PM: Eugene Ho.

• Referal Server: PM: Scott Johnson, Dev: Vincent Yung.

• Outlook: Accounts PM: Tadd Giles, Marketting Stats/Product Manager: David Delisi, PSS Stats: Todd Dooley, Accounts Dev Lead: Radu Bacioiu, Dev: Julia Cai.

•  

• IEAK: RFanco

• UI and PM: GSierra

• RFC Spec & Standards PM: JoshCo

• VPN UI: RaoS (Rao Salapaka) is probably the dev for the wizard.  DavidEi is the PM.  PMay (Paul Mayfield) \nt\private\net\routing\ras\ui\rasdlg\.

Open Concerns:

Shell Team:

• Question: Who will maintain server?  Answer: See microsoft.com.  

• Question: Who will buy the servers?  Answer: The shell team's cost center.  Office would also almost certainly be willing to pay for it.  Estimated Cost: $45k.  

• Question: Who will maintain the content?  Answer: Officially, Tadd Giles.  We will probably do a one time list of the top 30 servers and not change it much or at all after that.  

• Question: What % of users does the referal server not handle?   Answer: nnn%.  Stats from David Delisi.  

• Question: Does the referal server team see any problems?   Answer: See Referal Server

microsoft.com: (Doug Samper)

• They will own the server if Debrah Black signs off on the Business Purposal.

Referal Server: (Scott Johnson)

• Microsoft.com will run and maintain the servers.

• Question: Will 2 or 3 ISPs say that they will find it find it useful and they are happy with the information being provided?   Answer: I'm going to meet with them.

• Question: Make sure the user is informed that email associations won't configure accounts in legacy apps.   Answer: Easy to add to UI.

• Scott says that this solution will definitely cover significate cases that the referal server won't cover today.

Status:

• Design & Implemenation: The design is finished and the API is implemented.  TODO: 1) We can write high level automation interfaces for each of the AutoDiscovery specific users (VPN, vCard, etc.).  Currently, we only have email.  Callers can use low level API if we don't do the high level API.  2) Clean up the caching of data.  3) Change implementation to use final XML format (from RFC).

• XML Format After RFC suggestions: BryanSt needs to clean up the spec.  JoshCo will then send it around for suggestions and submission to as an RFC.

• UI & Products: GSierra needs to find out which products (e-mail in sepcific) are going to use the API.