118845 - test doc for downloading/saving UI

Status: VERIFIED FIXED

(Developer Documentation Graveyard :: General, defect, P2)

Description

[sairuh (rarely reading bugmail)]

spun off from bug 77820. need to have test doc for downloading UI, which would
cover:

* Save Page/Frame [and related variations]
* Save Link
* Save Image
* Download manager
* how/where one would encounter these features

will prolly be checked in at this location:

http://mozilla.org/quality/browser/front-end/testcases/file-handling/downloading.html

Comment 1

[sairuh (rarely reading bugmail)]

taking.

note: this is very much a work in progress. :) comments/suggestions still
welcomed, however.

Comment 2

[Bill Law]

I'd recommend all the test alluded to by my "download testing" document at
http://law.mcom.com/download.html.  I'll attach that to this bug for people
outside Netscape to examine (although some of the links on that page won't work
because those are on my server inside the firewall, also).

Comment 3

[Bill Law]

Attachment: Bill Law's download testing page

Comment 4

[sairuh (rarely reading bugmail)]

thanks, bill!

i should prolly chat with dawn re: putting those download test files externally,
eg, somewhere on the mozilla ftp site...

not sure what to do about the http tests,  unless i can place them somewhere on
the mozilla website w/o making cvs or the doctree hurt. or if there's an easier
way: i noticed that on http://mozilla.org, the nightly build links just have the
'http:' plopped in front. would that suffice?

[sorry about dropping the ball on this one, oh so long ago...]

Comment 5

[Bill Law]

No apology necessary.

Note that the files themselves aren't that big a deal (in fact, they usually
cause me grief because they're of a fixed content type and I usually want to
vary the content type).

Instead, we should examine the basic requirements:

1. We need to test with really small files (to catch
timing/progress-dialog-synchronization issues related to that).
2. We need to test with big files (to enable testing of progress-dialog stuff).
3. We need to be able to readily reproduce various content-type issues (that's
what my "gimme.html" makes easy by generating user-specified type content).
4. We need readily reproducible testcases for the various tricky stuff (content
encoding, caching, content disposition, etc.).

Also, my test page overlaps pure "download" testing with helper-app related
stuff.  They do tend to overlap, though.

Comment 6

[sairuh (rarely reading bugmail)]

yeah, because of the overlap i'll try to cross-reference btwn the downloading
and helper app test docs. :)

Comment 7

[sairuh (rarely reading bugmail)]

bug 121937 has an outline of download progress dialog tests which result from
File > Save Page As/accel+S.

iirc, those are all http downloads...so i should add another case[s] for ftp
downloads [since that progress dialog contains the pause/resume button, which
the http one lacks].

Comment 8

[sairuh (rarely reading bugmail)]

see bug 115176 for some test cases...as well as bug 121509 for saving re:
content-disposition [note the tests in the evangelism bugs that were blocked by it].

Comment 9

[sairuh (rarely reading bugmail)]

also see:

* bug 128667 comment 15 and 16
* bug 102353 comment 11, and related bug 102352

Comment 10

[James Cox]

accepting QA for mozilla developer docs.

some of these bugs have been around for a _long_ time. Reporters, would you
please review the bugs, see if the issues have been resolved, and close bugs
appropriately.

I will do a full review of all bugs not touched in one week (8th April). 

Thanks.

</spam>

Comment 11

[sairuh (rarely reading bugmail)]

resetting qa contact back to paul --since he's the primary person who currently
reviews/verifies my testdev stuff.

Comment 12

[sairuh (rarely reading bugmail)]

fixed/updated with v1.5. don't know when i'll get around to getting sample files
up on mozilla.org (sorry). but this is at a good 'pausing' point, so marking fixed.

see bug 139558 for the download manager page.

Comment 13

[Paul Wyskoczka]

v