Google Git
Sign in
chromium / external / github.com / WebKit / Speedometer / refs/heads/upstream/main
commita999ad102415cd8c2ff0b5c0e07e5a5d5d4e803c[log] [tgz]
authorCamillo Bruni <camillobruni@users.noreply.github.com>Thu Jul 25 07:03:30 2024
committerGitHub <noreply@github.com>Thu Jul 25 07:03:30 2024
treededa9c25b18527b1b16c513405b5f508f434d2e5
parente6e8a4f969d9aab04cee798de6fd1c6ef5ef6998 [diff]
Don't display invalid results (#406)

This partially fixes #399 by not display non-finite scores which are caused by 0-measured suite results.

- For non-positive or non-finite scores, the following summary page is displayed. Note that the detailed page is still accessible since you might find some useful information there.
- Additionally, a console.error is generated for each zero-sum suite
4 files changed
tree: deda9c25b18527b1b16c513405b5f508f434d2e5
  1. .github/
  2. resources/
  3. tests/
  4. .eslintignore
  5. .eslintrc
  6. .gitignore
  7. .npmrc
  8. .prettierignore
  9. .prettierrc
  10. about.html
  11. babel.config.json
  12. Development.md
  13. Governance.md
  14. index.html
  15. instructions.html
  16. InteractiveRunner.html
  17. LICENSE
  18. package-lock.json
  19. package.json
  20. README.md
  21. Testing.md
README.md

What is Speedometer?

Speedometer is a benchmark for web browsers that measures Web application responsiveness by timing simulated user interactions on various workloads. Our primary goal is to make it reflect the real-world Web as much as possible. When a browser improves its score on the benchmark, actual users should benefit. In order to achieve this, it should:

  • Test end-to-end user journeys instead of testing specific features in a tight loop. Each test should exercise the full set of what’s needed from the engine in order for a user to accomplish a task.
  • Evolve over time, adapting to the present Web on a regular basis. This should be informed by current usage data, and by consensus about features which are important for engines to optimize to provide a consistent experience for users and site authors.
  • Be accessible to the public and useful to browser engineers. It should run in every modern browser by visiting a normal web page. It should run relatively quickly, while providing enough test coverage to be reflective of the real-world Web.