Test Documentation for Type Ahead Find
Maintained by: Owen Marshall
Type Ahead Find is a new feature introduced in Mozilla
1.2. It allows the user, by merely typing in the open window, to automatically
search for links (or, even non-linked text) containing the typed text. This
Emacs-style search allows the user to search without use of the mouse or
difficult-to-remember key combinations.
What will & will NOT be tested
This outline is under development and is subject to change at any time.
We will need to cover:
- Type Ahead Find in the main browser window.
We will not need to worry about (at this
time):
- Type Ahead Find in Mail/News, Composer, etc.
Issues, references & bug information
Contact information
Reference materials
http://www.mozilla.org/projects/ui/accessibility/typeaheadfind.html--
Type Ahead Find UI specifications
http://lxr.mozilla.org/seamonkey/source/extensions/typeaheadfind/-- Type
Ahead Find source
Important bugs
Bug #30088
is currently tracking Type Ahead Find bugs. You can also:
Bug #158752
discusses additions of Type Ahead Find to mailnews and composer.
Bug #168281 reports how Type Ahead Find does not currently work with IME.
Bug filing information
Please, before filing another bug, be sure you have searched Bugzilla for any duplicate
bugs. Bugs for this feature should be in the Keyboard Navigation component of the Browser product.
To properly file a Type Ahead Find bug, please follow these steps (in addition
to following the bug writing guidelines):
- Assign the bug to the Browser product, in the Keyboard Navigation component.
- Include "typeahead" somewhere in the summary.
- Add "30088" to the "Bug XXXXXX Blocks" field.
- If you are filing this bug because the testcases failed, please be sure
that you can reproduce the bug. If you still see the bug after the second
test attempt, please include what test and at what step you were on when it
failed, and describe in detail the problem you experience in the bug report.
This will help developers and QA understand your bug.
If you don't feel comfortable with Bugzilla
or filing bugs, feel free to email me at malachi@bardstowncable.net. I am more than happy to look at your issue
and file a bug report as needed.
(top)
Test coverage and outline
Acceptance tests
These are intended to be the basic, acceptance level tests for Type Ahead
Find. All instructions are covered in taf_acceptance.html
- (Time: 1 minute) Test the ability of Type Ahead Find to locate a link
on the page.
Functional tests
These tests check the full abilities of Type Ahead Find. All instructions
are covered in taf_functional.html
- (Time: 1 minute) Test the full text search aspect (both linked and non-linked
text) of Type Ahead Find.
- (Time: 1 minute) Test that a URL and an email address can be navigated
to via the keyboard.
- (Time: 4 minutes) Test that Type Ahead Find properly responds to preference
changes.
- (Time: 2 minutes) Test keyboard combinations (Accel+[Shift]+G, [Shift]+F3,
etc.), along with repeated letter search.
- (Time: 2 minutes) Test wrap-around Type Ahead Find.
- (Time: 1 minute) Test keyboard combinations to cancel Type Ahead (Tab,
Esc, etc.).
Note that all times vary based upon a tester's experience, and the relative
amount of bugs (Type Ahead Find and otherwise) in the build the tester is
using.
What do I do if I find a problem while running
the tests?
Answer: If a bug doesn't already exist
in Bugzilla, file one, of course! Just remember, to get proper developer and
QA attention, you need to follow the above instructions.
(top)