QA/Execution/Web Testing/Meetings/2012-03-15: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 21: Line 21:
** Stephen talked to Paul McLanahan about steps QA can take when we see a perf issue (like [https://bugzilla.mozilla.org/show_bug.cgi?id=735867 bug 735867])
** Stephen talked to Paul McLanahan about steps QA can take when we see a perf issue (like [https://bugzilla.mozilla.org/show_bug.cgi?id=735867 bug 735867])
*** First step is to ask the developer if there's a DB query involved, and, if so, to work with them/IT to get the "slow-query log" (http://dev.mysql.com/doc/refman/5.1/en/slow-query-log.html)
*** First step is to ask the developer if there's a DB query involved, and, if so, to work with them/IT to get the "slow-query log" (http://dev.mysql.com/doc/refman/5.1/en/slow-query-log.html)
** We've used it before, but [http://webpagetest.org webpagetest.org] is now also being used (often!) by Web Prod + Flux, etc.
* We need a backup plan for Jenkins
* We need a backup plan for Jenkins


Confirmed users
9,511

edits

Navigation menu