How to check your computer before a weekend hackathon

A laptop that worked at home can become a problem when you need it for a full weekend of coding, calls, and demos. A flaky keyboard, weak battery, or unstable internet connection can cost you time when the team is waiting.

Run a check before you pack. Test Everything goes through the available hardware checks step by step and gives you a report, so you can spot issues while there is still time to fix them.

Check your computer before you go

Open Test Everything on the computer you plan to bring. Use the same browser and computer you will use at the event, and connect the charger if you are checking a laptop.
Follow the checks one at a time. Test the keyboard and mouse or trackpad, then check the screen, speakers, microphone, and camera if you expect to use them.
When a test needs the camera or microphone, allow the browser to use it if you are comfortable doing so. These checks need permission to access the device. You can still check the other hardware if you do not want to grant permission.
Run the network checks while connected to the Wi-Fi you expect to use, if possible. A result from home cannot guarantee the event network will be reliable, but it gives you a useful baseline.
Keep the computer on a hard surface with its vents clear during performance checks. Close demanding programs first, and avoid running a heavy test while you have unsaved work open.
Review the report and note any failed, unusual, or unavailable checks. Include what you noticed, such as a key that only works when pressed hard or a connection that pauses during a call.

A laptop's battery and charging checks appear only if the browser reports battery information for that device. If a check does not appear, that alone does not mean the hardware is faulty.

What the results mean

The checks respond as expected

If keys register, the screen shows its colors normally, and your audio and camera work in their checks, those parts of the computer are responding in the browser. This is a useful readiness check, not a guarantee that every app, driver, or event network will work perfectly.

A check shows a problem you can repeat

Repeat the test once, then check the same feature in a second app or setting. For example, if a microphone test is silent, verify that the operating system sees an input device before concluding the microphone is broken. A repeatable issue is a good reason to bring a backup, such as a wired mouse or headset.

A check is unavailable or needs permission

Some checks depend on the browser, device, or permission. Camera and microphone checks require permission, and battery information is not reported by every computer or browser. An unavailable check is not the same as a failed hardware test.

The network result changes

Wi-Fi and internet quality can vary with distance from the router, other people using the network, and the internet connection itself. A result at home measures that moment and location, not the event venue. For online collaboration, have a phone hotspot or another backup plan if you can.

Fix common problems before the event

Charge the laptop and check its adapter. Pack the charger and confirm the charging indicator changes when you plug it in. If the battery level does not rise, check the outlet, cable, and charging port before relying on that laptop all weekend.
Restart and retest a device that stops responding. Save your work, restart the computer, and close apps that may be using the camera, microphone, or audio output. This can release a device that another program has left busy.
Allow camera and microphone access. In Windows 11, open Settings › Privacy & security › Camera or Settings › Privacy & security › Microphone, and check access for apps and desktop apps. On macOS, open System Settings › Privacy & Security › Camera or System Settings › Privacy & Security › Microphone, then allow your browser. Also check the permission icon beside the browser address bar.
Choose the right audio device. On Windows 11, open Settings › System › Sound and select the correct output and input. On macOS, open System Settings › Sound and choose the devices under Output and Input. Make sure a headset is not muted or selected as the wrong device.
Reconnect loose accessories. Unplug and reconnect USB devices, try another port, and check Bluetooth pairing for wireless accessories. If a keyboard, mouse, or headset is unreliable, pack a spare or use the computer's built-in controls.
Check your Wi-Fi connection. On Windows 11, open Settings › Network & internet › Wi-Fi. On macOS, open System Settings › Wi-Fi. Reconnect to the correct network and test again near the router. If the internet itself is down, try another network rather than repeatedly changing the computer's settings.
Install important updates before you travel. Allow time for a restart and a retest afterward. Avoid starting an operating system or driver update just before the event if you cannot finish it and confirm the computer still works.

When a hardware problem needs a backup or repair

If the same key, port, screen area, or audio device fails after a restart and in more than one app, treat it as a real problem. Try a known-good accessory when that is practical. If the built-in keyboard or screen is unreliable, arrange repair or bring another computer rather than counting on a last-minute fix at the event.

What this check cannot predict

A browser check can show whether a device responds, but it cannot promise that a coding environment, account login, project, or venue network will be ready. Open the apps and files you need before leaving, bring your charger, and keep a copy of important work somewhere you can access offline.

Most hardware checks run on your device. The speed tests exchange test data with our server to measure the connection, and your project files are not needed for the inspection.