We have recently revived the dev channel and plan to update it frequently. We need help from our volunteers in the open source community, especially in the form of bugs. One of the goals of the project is to iterate quickly and getting there involves finding, fixing and validating the bugs as soon as possible is very important to stabilize the builds.
Many of you have been helping us by filing bugs as well as by helping triage issues. This help has been invaluable to us and we decided to try out some new ideas to get more structured feedback from the community. As an experiment, we have posted some of the test cases that our testers run through on the chromium.org site and would like you to help us validate them. These are fairly simple test cases and should not take more than an hour or so to validate them all. You can choose to validate as many as you wish. All help is welcome! Here is where you can find all the test cases as well as instructions on how to report the results as well as some other general guidelines: http://sites.google.com/a/chromium.org/dev/for-testers/test-cases. Since this is an experiment, we have restricted the number of test cases to around 10 in the first iteration. As we get more feedback from the field, we will try and increase the scope of this exercise if the data looks promising. Lastly, we'll be sending a follow-up survey to all those who participate in this exercise, which will help us evaluate it better. If you have questions/feedback about specific test cases, please email me directly. Thanks, Niranjan (on behalf of the Chromium test team) --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
