https://github.com/brycewray/browser-tests
PROJECT NOW CONCLUDED.
https://github.com/brycewray/browser-tests
benchmarking browser linux macos testing
Last synced: about 2 months ago
JSON representation
PROJECT NOW CONCLUDED.
- Host: GitHub
- URL: https://github.com/brycewray/browser-tests
- Owner: brycewray
- License: mit
- Created: 2023-12-11T11:03:39.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-01-12T14:54:29.000Z (over 2 years ago)
- Last Synced: 2025-05-16T12:40:00.531Z (about 1 year ago)
- Topics: benchmarking, browser, linux, macos, testing
- Homepage:
- Size: 122 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Browser tests
> [!NOTE]
> This project is [concluded as of 2023-12-27](https://www.brycewray.com/posts/2023/12/testing-testing-ending-fools-errand/).
----
This is where I keep version-controlled tests on [various web browsers](/browsers.md), along with [the files I originally maintained before deciding this project’s output was worth VC’ing](/pre-git).
The tests are on browsers in [macOS](/macos-2023-mac-studio.md) and [Linux](/fedora-linux-2017-imac.md). All timestamps within are in U.S. Central time (CDT/CST), with dates in `yyyy-mm-dd` format.
> [!NOTE]
> I have no **reliable** way to run tests in Windows. I am using Macs: an Apple Silicon model for macOS, and an Intel model for Linux. While the Apple Silicon Mac does have Parallels Desktop emulation of the ARM version of Windows 11, I’ve noticed enough oddities in running browsers on that setup — *e.g.*, Chrome always installs as “emulated 32-bit” and Brave refuses to auto-update — that I simply don’t trust test results from Windows 11 on ARM, period, much less from **emulated** Windows 11 on ARM.