QA/TDAI/Meetings/2006-12-18: Difference between revisions

no edit summary
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
* Test Development, Automation, Infrastructure Discussion
<small>[[QA/TDAI/Meetings|index]] | [[QA/TDAI/Meetings/2007-01-05|next mtg »]]</small>
* Dec 18th, 2006
 
'''Test Development, Automation, Infrastructure Discussion''' - Dec 18th, 2006


= Attendees =
= Attendees =
Line 51: Line 52:
* Look at what buildbot displays
* Look at what buildbot displays
** easy to extend
** easy to extend
* Long running tests can still be run and reported with one of rh late night builds
* Long running tests can still be run and reported with one of the late night builds
* Litmus advanced query would be useful for future data mining and non-tinderbox oriented reporting  
* Litmus advanced query would be useful for future data mining and non-tinderbox oriented reporting


== Plans/ideas  for test extension ==
== Plans/ideas  for test extension ==
*  Seneca - David Hamp-Gonsalves
New tool available from Seneca College
** Developed by David Hamp-Gonsalves
** See [http://zenit.senecac.on.ca/wiki/index.php/Bug_Triage_Extension Seneca College Project - Buggy Bar]
** See [http://zenit.senecac.on.ca/wiki/index.php/Bug_Triage_Extension Seneca College Project - Buggy Bar]
** grabs next unconfirmed bug from bugzilla
** Grabs next unconfirmed bug from bugzilla
** Good as long as bug is formatted by the bug submitter tool
** Good as long as bug is formatted by the bug submitter tool
** Updated bug with confirmed status and comments
** Waiting for AMO group to sign off on Buggy Bar
*** Add to comment: confirmed via buggy bar
** Updates bug with confirmed status and comments
*** Tracy to check if he can add unique text in comment so we can see how this is working.  '''<<== AI tracy'''
*** Add to comment: "confirmed via buggy bar" or something similar so we can see how may bugs are being processed by this extension?
*** Tracy to check if David can add unique text in comment so we can see how this is working.  '''<<== AI tracy'''
** He has offered to create a litmus extension
** He has offered to create a litmus extension
*** tracy - to lead this '''<<== AI tracy'''
*** tracy - to lead this '''<<== AI tracy'''
** Waiting for AMO group to sign off on Buggy Bar
 
* RefTests - not good candidates for test ext
* RefTests - not good candidates for test ext
* Other testing extensions [bob]
* Other testing extensions [bob]
** Spider - general purpose
** Spider - general purpose
*** Fire off JS events
*** Fire off JS events
*** See blog - about attempting to driver browser from KB, Mouse events, fill in forms, etc.
*** See [http://bclary.com/blog/2006/11/28/spider-and-firefox-automation/ Bob's blog] - about attempting to drive browser from KB, Mouse events, fill in forms, etc.
*** Spider is currently very user un-friendly but a lot of potential
*** Spider is currently very user un-friendly but a lot of potential
*** Next step: discuss on weekly JS test automation mtg
*** '''Next step''': discuss in weekly JS test automation mtg


== Extending search engine/trademark verifiers (search enginers, rss feeds, search strings, etc) ==
== Extending search engine/trademark verifiers (search enginers, rss feeds, search strings, etc) ==
* Didn't get to this
* Didn't get to this
1,457

edits