Getting Started
For mass testing on production line, before testing :
- Make sure the TestQC server is online and available
- Make sure the Ethernet or WiFI network is ready (SSID name and password)
- Quiet environment and enough room lighting (important for mic, speaker and webcam test)
- Line up device under test and usb barcode scanner for serial number scan.
Although initially this web version of TestQC was intended to test chromebook models that already have a built-in chrome browser, this web version of testqc can also be used to test the regular notebooks with their pre-installed OS or even android/iOS tablets and smartphones with their default browser preferences.
Some tests may not run properly on that other devices, but mostly just because the peripheral is not available on the device.
The following below is a summary of the steps to test on each device :
- Connect to the network
- Open TestQC Web with url
https://xx.xx.xx.xx - Do the Testing (Keyboard, Deadpixel, Touchscreen … and so on)
- If done, then Press Submit / Upload button
- Scan the barebone Serial Number (SN ID) or manually input the Serial number
- Submit the report test
- Shutting down
TestQC HTTPS URL
Pay attention to the https protocol on the URL since some test needs https to work. This has been resolved recently by redirecting all http request to https automatically. However, since this is a local server that doesn’t have FQDN to apply Let’s Encrypt certs, user still must answer the confirmation from browser :Proceed to unsafe connection
The TestQCWeb application is a web-based version of TestQC that runs entirely in your browser. Because it operates in a secure, sandboxed environment, it cannot directly access or retrieve hardware component data from your device.
If you need detailed component-level data retrieval, please use one of the other available variant versions of TestQC app :
- TestQCUSB : The primary version of this TestQC app that runs on Linux as a Live USB. No installation needed.
- TestQCWin : A native Windows version that relies on OEM drivers for maximum hardware compatibility.
Web browsers intentionally restrict access to low-level hardware data for security and privacy reasons — and rightly so. You can imagine how thrilled hackers would be if a website could just peek at your device’s internals without permission. 😏
“This isn’t a privacy choice — it’s literally impossible for web browsers to access that level of hardware data.”
Because TestQCWeb runs entirely within your browser, it is not affected by driver or kernel compatibility issues, making it the most universally accessible version of TestQC. It’s ideal for quick tests, remote diagnostics, and platforms where installing software or drivers isn’t possible.