Closed
Bug 991664
Opened 11 years ago
Closed 4 years ago
Test Automation for PluginCheck
Categories
(Websites :: plugins.mozilla.org, defect, P2)
Websites
plugins.mozilla.org
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: espressive, Unassigned)
References
()
Details
Merging in a discussion started via email for further discussions:
Schalk ping'd and asked for an audience; plugin check is seeing new development and the team has begun noticing a number of regressions and new bugs that automation could potentially limit as well as catch before code lands on prod.
The plugin check site is ranked as the #2 site (#1 is mozilla.org) that the public lands on. I would suggest we identify scenarios that should never fail - start with happy path smoke tests - and automate those first.
We also need to identify infrastructure requirements and discuss how to solve these hurdles as well as if and what we can reasonably accomplish within time frame constraints. Example; how to effectively spin up and maintain different instances of multiple OSes with specific versions of Flash (etc) installed that the tests can run against.
Cheers,
Matt Brandt
| Reporter | ||
Comment 1•11 years ago
|
||
Do we know where most visits to the site are coming from? If a number are coming from the Firefox UI, then we might want to have automated testing that spans coming from that UI and interacting with the page. And that leads me to wonder if we also need some Firefox automation there, so adding Henrik here.
KaiRo
| Reporter | ||
Comment 2•11 years ago
|
||
We have remote tests in the mozmill-tests repository, which are targeted
to run tests between the application and a website. Our tests are not
limited to localhost, so we can indeed test the live site!
We have machines across all platforms and version, and Flash is
installed. But only the latest and most secure version. As of now we
cannot flip between different versions of it. So for those requirements
a dedicated system might be preferable. We should be able to help you in
figuring out what's necessary. Just let us know.
-- Henrik Skupin Software Engineer in Test Mozilla Corporation
PluginCheck is no longer supported
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•