Automate litmus test Testcase ID #5061 - Completed download - context menus

ASSIGNED

Status

()

Toolkit
Downloads API
ASSIGNED
10 years ago
10 years ago

People

(Reporter: Anoop Saldanha (Poona), Assigned: Anoop Saldanha (Poona))

Tracking

(Blocks: 1 bug)

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

10 years ago
Proposed type of test: chrome

Proposed location of test: toolkit/mozapps/downloads/tests/chrome
(Assignee)

Comment 1

10 years ago
Created attachment 331156 [details] [diff] [review]
v1.0

The test passes.  Actually I thought of clubbing this with 447830 and 447831.  But since the litmus tests were separate and the tests seemed to give a separate identity to contextmenus of each kind of download, I separated the 3 tests.
Attachment #331156 - Flags: review?(sdwilsh)
(Assignee)

Comment 2

10 years ago
Created attachment 331499 [details] [diff] [review]
v2.0

Test updated to accommodate the updated utils.js.  The test passes.
Attachment #331156 - Attachment is obsolete: true
Attachment #331499 - Flags: review?(sdwilsh)
Attachment #331156 - Flags: review?(sdwilsh)
Product: Firefox → Toolkit
Comment on attachment 331499 [details] [diff] [review]
v2.0

I was about to say that the litmus test in question wasn't worth being a test, but then it occurred to me that we have different menus for different states of the downloads.

So, instead of checking string values, we should just be checking the command attribute on the menuitems.  Those won't ever change, and it's more reliable and easier than getting the strings.
Attachment #331499 - Flags: review?(sdwilsh) → review-
You need to log in before you can comment on or make changes to this bug.