FirefoxSummit/2006/ProposedSessions/CommunityTestingAndLitmus/Notes: Difference between revisions
Jump to navigation
Jump to search
Zachlipton (talk | contribs) No edit summary |
Zachlipton (talk | contribs) No edit summary |
||
| Line 12: | Line 12: | ||
* Make testing calendar more widely known, publicize dates better. | * Make testing calendar more widely known, publicize dates better. | ||
* Send automatic email to new Litmus testers after they've done some testing to introduce Mozilla QA + provide resources to get more involved. | * Send automatic email to new Litmus testers after they've done some testing to introduce Mozilla QA + provide resources to get more involved. | ||
* More creative testdays--task oriented. | * More creative testdays--task oriented tests. | ||
* Let people create their own testcases and groups specific to content and sites they interact with regularly. Mix and match existing testcases and new tests. | |||
Revision as of 23:57, 16 November 2006
Stats
- Now nearly 3500 testcases
- About 850 active testers out of the 2000 who have accounts.
- Not seeing much overlap between testdays, only a few people come back.
- Of the top testers, several community members keeping pace with MoCo staff testers.
- Dip in number of testers Aug/Sep -- one was Thunderbird which historically has less interest, and we had a lot of testdays around the same time, community getting burned out?
Test days
- Seneca testday 2006-11-03 with 35 testers. Harness that kind of support in an ongoing basis? Seneca students assigned to come, most probably won't come back.
- Trying to reward people with shirts and such, but we can't keep doing it to attract people
- School/university support
- Make testing calendar more widely known, publicize dates better.
- Send automatic email to new Litmus testers after they've done some testing to introduce Mozilla QA + provide resources to get more involved.
- More creative testdays--task oriented tests.
- Let people create their own testcases and groups specific to content and sites they interact with regularly. Mix and match existing testcases and new tests.