Feature Test Plan

The Mozilla Organization
	At A Glance
	Feedback
	Get Involved
	Newsgroups
	License Terms
	Newsbot

Developer Docs
	Roadmap
	Projects
	Ports
	Module Owners
	Hacking
	Get the Source
	Build It

Testing
	Download
	Bugzilla
	Bug Writing

Tools
	View Source
	Tree Status
	New Checkins
	Submit A Bug

FAQ
Search

Feature Test Specification

Seamonkey (5.0)
Autofill/Password Manager (Single-Signon)

Written by: <Paul MacQuiddy>

History:

Date Change Description Revision Updated By

4/27/99 First Draft .9 Paul MacQuiddy

10/16/99 Sanitized Draft for mozilla.org 1.0 Paul MacQuiddy

References:
UI and/or Functional Specifications:

PRD: http://client/seamonkey/prd/walletprd.htm An internal Netscape link to Kevin Yen's marketing documents detailing what wallet is and why people want it.
Engineering Specifications: http://webgroup/xpnav/ An internal Netscape link to Steve Morse's engineering spec on how wallet works.

Wallet is a feature/service that allows the consumer to automatically fill (the most commonly required) fields in e-commerce forms. This is so you don't have to manually type in your name, address, phone#, etc, every time you buy a pencil on the internet. The feature is extended to include the auto-fill of username and passwords that have been chosen to be saved, which will be called 'Password Manager (formerly SingleSignon)'. The two features are related but will be tested separately.

Won't Test Areas:

Different sites use different names for their fields. Autofill has a method that maps the various field names from one site to another. This will only be tested on an adhoc basis.

Major Issues:

The UI for both features are still TBD. XUL overlays are planned to be used for discoverability, however, they are not yet implemented.

Functional test cases

Autofill

Activating Wallet - The first time you submit a form, you will be informed of the Autofill feature. Make sure the text in that dialogue is informative and accurate
Capture Form - Capture Form is used to populate your personal database with your various info. There are two ways to check this, one way is to look at Wallet Contents and the other way is to use Safe Form Fill. Both ways will be checked. There are rumours that Capture Form will be accessed via a XUL overlay on forms pages. There may also be a menu item (current implementation). The interview page (Edit | Wallet | Samples | Click Here) has a form with all the available fields. Use it!
Edit Wallet Contents - Your personal info can be modified, deleted, and added to in the Wallet Contents menu item, currently under Edit - Wallet. Basic functionality will be tested.
Safe Form Fill - When you choose to Autofill (currently called Safe Form Fill) a dialog pops up with the list of fields you can autofill. This dialog will be tested. Test when some forms are already partially filled. Test choosing just some of the available fields. This functionality will be available via a XUL overlay in the future. Currently it is in the Edit | Wallet menu.
Ad-Hoc Testing - Currently there is a Samples menu item under Edit | Wallet that should be thoroughly tested for interoperability between sites.

Single Sign-on

Activating Single Sign-on

First time you authenticate - The first time you submit a signon, you are informed of the Password Manager feature and asked if you would like to enable it. Confirm that the text is informative and accurate.
Enabling thru preference item - You can also turn it on via preferences after you have turned it off. Confirm this works.
Setting passwords - The Password Manager has a password of it's own you must set, thus the term single signon. Setting the password will be tested. Currently there are two consecutive dialogues to confirm your password is accurate, there may be one in the future.

Saving (or not saving) a Sign-on

After enabling the password manager, we must test that you can save a signon successfully. To verify the username,check in the menu item Edit | Wallet | Display Signons. To confirm the password is correct, you must re-start and use a remembered a signon.
You can choose to not remember a signon. You can then choose to remember that decision. In other words, you should be able to go back to that site, submit a signon, and you will not be asked if you want it saved. Please test this!

Using a Remembered Sign-on

With just one signon already saved
With multiple signons at same site

Viewing/Editing Single Sign-on

Deleting signons will be tested.
Viewing Signons not saved will also be tested.

Browser Generated Forms

username/password at http sites - We must make sure that http authentication takes full advantage of the Password Manager.
username/password at ftp sites - We must also make sure that ftp authentication takes full advantage of the Password Manager.

Disabling Single-Signon - Single Signon can be disabled from ever asking you if you want signons saved by unchecking the pref in the Advanced pane. It should also not ask you for your password when you goto sites where you have saved signons in the past.
Change password - You can change your password once you have set it. Confirm this works properly, and is persistent.
Ad-hoc testing

Common sites (E*TRADE, Optionslink, E-Bay etc)