Browserscope

Browserscope FAQ

  1. I just ran the tests, why don't I see my score there yet?
  2. How many times can I run the tests?
  3. How do I contact the developers / is there a discussion group?
  4. I think I found a bug, where can I submit it?
  5. Where does the data come from and live?
  6. Have you considered selection bias in the results?
  7. Do I need to sign in to run the tests and send in my scores?
  8. Is Browserscope open-source?
  9. How can I contribute code or tests to Browserscope
  10. When did Browserscope go live?
  11. Who all's involved so far?
  12. Where is Browserscope being hosted?
  13. What license is the data released under?
I just ran the tests, why don't I see my score there yet?
The backend system is playing catchup as new scores come in. We promise we didn't lose your score =)
How many times can I run the tests?
The system will only count your score toward the totals a certain number of times per day, but you're welcome to run the tests as many times as you like.
How can I contact the developers or discuss this project?
Please visit groups.google.com/group/browserscope or send an email to browserscope@googlegroups.com.
I think I found a bug, where can I submit it?
Please check to see that it hasn't already been filed - we have issue tracking set up at code.google.com/p/browserscope/issues/list
Where does the data come from and live?
The data comes from developers and users like you, running the tests in their browsers. At the end of the tests, the results are sent back to the Browserscope database which is hosted on Google App Engine. An MD5-hashed version of the IP address that submitted the test is saved to prevent abuse.
Have you considered selection bias in the results?
We've given this a lot of thought actually, but we'd always love to hear your views on how to improve the system in this regard. That said, our thoughts are:
  • A wide variety of users run the tests, giving greater coverage than would be possible from a typical regression test suite.
  • Tests are run under real world conditions. Results are aggregated across all tests, reducing the impact of bias and outliers.
  • Because testing is in the hands of users, it's always up-to-date. As soon as a new browser or web device comes out, it shows up in Browserscope. Often, it shows up beforehand as part of developer beta testing.
Do I need to sign in to run the tests and send in my scores?
No, you do not need to sign in. However, if you do sign in before running the tests, your Google userid is stored along with your test results in order to eventually make it possible for you to retrieve all your scores.
Is Browserscope open-source?
Browserscope is an open source project, licensed under the Apache 2.0 license with all of the code publicly hosted at code.google.com/p/browserscope.
How can I contribute code or tests to Browserscope?
  1. See the instructions above and checkout and run the codebase on your workstation.
  2. Make edits/additions in your code tree and create a patch. (Does your code need unit tests? Check out the unit tests in the /tests directory and add tests for your changes there.)
  3. Create an issue for tracking your new code at code.google.com/p/browserscope/issues/list and upload your patch there. We'll get you some feedback ASAP!
When did Browserscope go live?
Sep. 14th, 2009 - Read the launch announcement blog post
Where is Browserscope being hosted?
Browserscope is powered by Google App Engine
What license is the data released under?
The data is dedicated to the public domain under the CC0 1.0 Universal Public Domain Dedication (http://creativecommons.org/publicdomain/zero/1.0/).
Who all's involved so far?

code.google.com/p/browserscope/people/list

CC0 | Home | FAQ | API | UA Parser | News | Browser Resources | Code | Submit a Bug | Downloads | Mailing List | Contact