Closed Bug 169954 Opened 22 years ago Closed 22 years ago

Smoketests need to include Typeahead find testing

Categories

(Developer Documentation Graveyard :: General, defect)

x86
Other
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 170561

People

(Reporter: owen.marshall+bmo, Assigned: tracy)

References

()

Details

In my opinion, the smoketest page needs to be updated to include a simple test
to be sure typeahead find works.

--> twalker@netscape.com
I'm not the one to make this decision.  But I will look into it.
Let me ask this: If autofill doesn't work, would that failure be cause to keep 
the tree closed?  
Asa, Aaron, what do you think?

Items added to smoketests have to get by-in from development that the sheriffs
will hold the tree closed to all check-ins if a smoketest fails.   Normally an
item in the smoketest covers a major component which prevents further testing. 
Also, we want to keep smoketests to a manageable number that can be completed in
a timely fashion.
I don't think other development needs to get held up when there's a problem with
type ahead find. But I do think we need to come up with a test plan for
typeaheadfind sometime in the next month. 
if i have time, i can prolly whip up a quick test outline for type ahead find.
filed bug 170561.

my own $0.02: i really don't think this feature should be part of the smoketests.
Hmm, all right then =) I guess, as long a test exists somewhere, it's all good.
I only knew about the smoketests -- wasn't sure that another set even existed.

As long as no one else objects...

*** This bug has been marked as a duplicate of 170561 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified dupe
Status: RESOLVED → VERIFIED
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.