FirefoxSummit/2006/ProposedSessions/CommunityTestingAndLitmus/Notes: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 18: Line 18:
* Email out testday notifications to people who came to previous test days.  
* Email out testday notifications to people who came to previous test days.  


== Manual test execution ==  
== Manual test execution/Ways Litmus can help ==  
* Partner testing
* Partner testing
** Security flags for testcases
** Security flags for testcases
Line 27: Line 27:
* Display with checkboxes for admins to check off when results have been appropriately dealt with
* Display with checkboxes for admins to check off when results have been appropriately dealt with
* Programmatic regression analysis--determine when tests began failing and find the delta
* Programmatic regression analysis--determine when tests began failing and find the delta
* Daily digest email from Litmus, giving failures and stats from the day's testing
* Daily digest email from Litmus, giving failures and stats from the day's testing -- Bug 360996
   
   
* Testcases in other languages.
* Testcases in other languages
** Let the localizers take care of the results
** Do localizers really need tests in their own language?
** Create new l10n suite of tests that are sensitive to locale changes
 
* Easy way to tag tests/make a small list of tests to point people to around a specific area
 
* Test group editing is foobar'd
 
== Test Runs ==
* Right now a very freeform testing interface. Need a better way to target testers to what we need help with right now
* Adding an extra Test Run layer doesn't really add much functionality
* Homepage to point people towards what we want to test
* Limiting - test a particular build id on certain platforms
* How is a run different then a group?
* Run is a bucket of tests with a limited lifetime or permanent 
* Make it simpler, point people to the build and the tests--pimp it to them up front
314

edits