Closed Bug 657486 Opened 13 years ago Closed 13 years ago

Mozmill test for "Loading" status of the AOM Discovery Pane

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: u279076, Assigned: u279076)

References

()

Details

(Whiteboard: [mozmill-restart][aom-discovery] )

Tracking bug to develop a Mozmill test for the following Litmus test:

Check the "Loading" status for the discovery pane
https://litmus.mozilla.org/show_test.cgi?id=15368
Whiteboard: [mozmill-test][aom-discovery] → [aom-discovery]
A Pivotal Tracker story has been created for this Bug: https://www.pivotaltracker.com/story/show/13465875
Assigning to myself.
Assignee: nobody → anthony.s.hughes
Status: NEW → ASSIGNED
After consulting with WebQA, it's been determined that only tests which test installing add-ons need to be automated in Mozmill. Resolving WONTFIX.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Anthony Hughes deleted the linked story in Pivotal Tracker
(In reply to comment #0)
> Check the "Loading" status for the discovery pane
> https://litmus.mozilla.org/show_test.cgi?id=15368

Why is there a Litmus test? This is not content related but at the chrome side of Firefox. It has already Mochi tests so we could completely get rid of this Litmus test. Krupa or Marlena, can one of you please disable that test?
I added it since it was one of the scenarios not covered by Selenium and I was requested to add testcases which needed coverage. Glad that it already has coverage.

Content on disco pane takes a while to load (mostly due to CDN issues) and this is a good test to see that we are showing a "loading.." message to our testers based in other countries. It will not hurt to have coverage for this in Litmus.
Whiteboard: [aom-discovery] → [mozmill-remote][aom-discovery]
Whiteboard: [mozmill-remote][aom-discovery] → [mozmill-restart][aom-discovery]
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.