Skip to content

Getting Started

Preparation

Before mass testing on the production line, the following steps must be taken:

  • Ensure that the TestQC server is online and available.
  • Make sure that the Ethernet or Wi-Fi network is ready. This includes knowing the SSID name and password.
  • Prepare a quiet environment with enough room lighting. This is important for mic, speaker, and webcam tests.
  • Line up the devices under test and the USB barcode scanner.

Compatibility

Basically, this USB TestQC TUI is built on a Linux OS with the latest Linux kernel to support compatibility with the latest hardware required on the latest chipset or platform releases on laptops or notebooks. However, hardware changes rapidly these days, and the Linux kernel may not yet support the latest platform. Therefore, this USB TestQC TUI should always be updated with the latest kernel and firmware to maintain compatibility with new hardware changes.

Standard Operating Procedure

The following below is a summary of the steps to test on each device :

  • Boot the TestQC TUI LiveUSB
  • Check the Device Info List (Component List)
  • Connect to the network
  • Do the Testing (Keyboard, Deadpixel, Harddisk ... and so on)
  • Scan the barebone Serial Number (SN ID) or manually input the Serial number
  • Submit the report test
  • Shutting down

See the step by step in details for Testing Procedure.

Boot from USB

In Legacy BIOS systems, you can select a boot device by setting the boot priority in the BIOS setup menu or by using the F12 boot device menu.

In UEFI systems, you must first disable Secure Boot in order to boot from a USB flash drive. This is because Secure Boot is designed to prevent the computer from booting from unauthorized devices. Once Secure Boot is disabled, you can boot from the USB flash drive by setting it as the first boot device in the BIOS setup menu.

Limitation and Disclaimer

This TestQCTUI is a Linux-based tool that is designed to test a wide range of hardware. However, some of the latest chipset / peripheral hardware platforms may not be fully supported by the Linux kernel. This can result in the device not being detected or not working properly. The most common hardware that is affected by this issue is usually networks and sound cards. When this issue occurs, it can cause a significant problem, especially if testing has to be done for production or distribution and the deadline cannot be rescheduled.

If hardware compatibility issues occur, you can use one of the other available variant versions of TestQC app :

  • TestQCWin : A native Windows version that relies on OEM drivers for maximum hardware compatibility.
  • TestQCWeb : A browser-based version that runs directly in any modern web browser and does not depend on local drivers.

These limitations are not caused by TestQCTUI or Linux itself. Linux actually supports a wider range of hardware than any other operating system. The problem is that hardware vendors are often slow to release drivers for Linux. As a result, there may be a delay before the latest hardware is fully supported by Linux. If you are experiencing problems with the TestQCTUI on a specific hardware platform, you can report the issue to the developers. They will be able to investigate the issue and work with the hardware vendor to release a driver for Linux.