114081 - Front End tests: Bookmarks: doc errors

Status: VERIFIED INVALID

(Developer Documentation Graveyard :: General, defect)

Description

[Jay Farrell]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    2001112013

A few of these tests (like show-hide-folder) mention a "Disclosure Triangle". I 
think they mean the box that has a + or - in it for
folders that can be opened or closed. This terminalogy should change.

For test rename-bookmark, step 2 indicates that highlighting a bookmark in 
manage bookmarks will allow you to directly edit it.
(Expected Results step 1 also says this).  I've found on both OpenVMS
and Linux that this is not the case. You need to click on rename in
order to change the bookmark's name. (There are many "rename"s to click on, and 
they all work.)  The document for this test should be
updated to reflect this.

Reproducible: Always
Steps to Reproduce:
1.see documentation for Show-hide-folder and rename-bookmark
2.
3.

Actual Results:  incorrect documentation info

Expected Results:  correct documentation info (?)

Comment 1

[Asa Dotzler [:asa]]

Are you talking about the tests located at
http://www.mozilla.org/quality/browser/front-end/testcases/bookmarks/ ?
If so then this should probably be assigned to claudius. 

(On most documents at www.mozilla.org you can click the Document History link at
the bottom of hte page to see who is maintaining the document. If it's obvious
who owns the doc feel free to assign the bug directly to them.)

Thanks for reporting these bugs, Jay. 

Comment 2

[Claudius Gayle]

1st, the #1 rule of bug writing is 1 bug per bug report, please.
2nd thank you for running these test or even just reading them. I appreciate the
feedback and by all means continue to do so.

finally, these bugs are both invalid.
At the time this bug was written, the disclosure triangles may very well have
not been visible, likely because we were switching from trees to outliner
widgets and outliner was not ready to handle images yet. As for rename the
testcase is designed to test the 'inline-rename' feature, which as indicated on
the test matrix is as yet unimplemented. Anyway, testcases sit
above the day-to-day quirks of a build. They are written against a spec or per
my good judgement (in consultation w/peers) where none exists. They will not
change to reflect the builds. Rather, the builds should change to reflect the
specs (and by derivation the testcases). This process is how we know bugs are bugs.

resolved INVALID

Comment 3

[Claudius Gayle]

VERIFIED Invalid