QA/Mozmill Test Automation/Endurance Tests/Meetings/02-15-2011: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "<small> Endurance Tests Home | next mtg » </small> = Discussio...")
 
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 4: Line 4:


= Discussion Items / Updates =
= Discussion Items / Updates =
* Initial tests and shared-module [http://hg.mozilla.org/qa/mozmill-tests/rev/25f5f895535d landed on default!]
* Started work on patch for running endurance tests with add-ons installed for investigating/replicated memory leak issues:
** [https://bugzilla.mozilla.org/show_bug.cgi?id=630072 Bug 630072] - quora.com bloats out of control, part 1: js_UnbrandAndClearSlots leaks
** [https://bugzilla.mozilla.org/show_bug.cgi?id=631494 Bug 631494] - Massive memory leak with Adblock Plus 1.3.3 installed
*** It looks like this is resolved (at least according to the [https://bugzilla.mozilla.org/show_bug.cgi?id=631494#c85 Endurance Tests metrics]).
** [https://bugzilla.mozilla.org/show_bug.cgi?id=633382 Bug 633382] - Xray wrappers don't cache resolved native properties on the holder object
* We need [http://etherpad.mozilla.com:9000/mLWlTg7DwK more tests!]
** Panorama?
** Flash content?
* Page timeouts have been seen when loading external content. Should we increase the timeout? Is there an ethical issue with repeatedly requesting the same external page?


= Project Status / Goals =
= Project Status / Goals =
* We're looking really good for the phase I goals. Perhaps we need to reassess our goals for Q1?


= Takeaways and Action Items =
= Meeting Notes =
* We should speak to the guys responsible for Graphxbot to see where we can reduce duplication of efforts - they already gather detailed system information.
* We should ultimately serve any flash content from the webserver that Al's setting up.
* In the automated test runs we should limit the amount of external sites to avoid being perceived as attacking them. Any tests that hit external sites a lot should be run ad-hoc.
 
= Action Items =
* Raise a bug for running endurance tests with addons (Dave)
* Raise a bug for caching metrics to disk instead of memory (Dave)
* Raise a bug to add endurance test compatibility to the crowd extension (Dave)
* Add readme for endurance tests (Dave)
* Create an endurance test for Panaroma (Anthony)
* Source a flash video to serve as local content (Anthony)
* Find out if we can run restart endurance tests (Dave)
* Find a contact in the Talos team so we can start to investigate gathering similar metrics. Joel Maher is an active contributor. (Dave)
* Continue to investigate using endurance tests to replicate the bugs mentioned above. (Dave)

Latest revision as of 23:43, 15 February 2011

Endurance Tests Home | next mtg »

Discussion Items / Updates

  • Initial tests and shared-module landed on default!
  • Started work on patch for running endurance tests with add-ons installed for investigating/replicated memory leak issues:
    • Bug 630072 - quora.com bloats out of control, part 1: js_UnbrandAndClearSlots leaks
    • Bug 631494 - Massive memory leak with Adblock Plus 1.3.3 installed
    • Bug 633382 - Xray wrappers don't cache resolved native properties on the holder object
  • We need more tests!
    • Panorama?
    • Flash content?
  • Page timeouts have been seen when loading external content. Should we increase the timeout? Is there an ethical issue with repeatedly requesting the same external page?

Project Status / Goals

  • We're looking really good for the phase I goals. Perhaps we need to reassess our goals for Q1?

Meeting Notes

  • We should speak to the guys responsible for Graphxbot to see where we can reduce duplication of efforts - they already gather detailed system information.
  • We should ultimately serve any flash content from the webserver that Al's setting up.
  • In the automated test runs we should limit the amount of external sites to avoid being perceived as attacking them. Any tests that hit external sites a lot should be run ad-hoc.

Action Items

  • Raise a bug for running endurance tests with addons (Dave)
  • Raise a bug for caching metrics to disk instead of memory (Dave)
  • Raise a bug to add endurance test compatibility to the crowd extension (Dave)
  • Add readme for endurance tests (Dave)
  • Create an endurance test for Panaroma (Anthony)
  • Source a flash video to serve as local content (Anthony)
  • Find out if we can run restart endurance tests (Dave)
  • Find a contact in the Talos team so we can start to investigate gathering similar metrics. Joel Maher is an active contributor. (Dave)
  • Continue to investigate using endurance tests to replicate the bugs mentioned above. (Dave)
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Mozmill_Test_Automation/Endurance_Tests/Meetings/02-15-2011&oldid=284940"