Skip to main content Scroll Top

Build Week 6: Testing Everything Before Anyone Else Does

The sixth stage in our Build Week series is testing. Content is in, features are connected and the site looks finished. Testing is where the team tries, deliberately and methodically, to find what is broken before a customer does. It is not the glamorous part of a project, but it is often the stage that determines whether launch day is calm or chaotic.

Devices and browsers

A website can look perfect on the designer’s screen and fall apart elsewhere. Testing usually covers a range of real situations:

  • Phones of different sizes, held both upright and sideways.
  • Tablets and laptops as well as large desktop monitors.
  • The current versions of the major browsers.
  • Slower connections, which reveal heavy pages and slow images.

Testers look for overlapping text, buttons that are hard to tap, menus that do not open, images that crop badly and anything that forces sideways scrolling.

Advertisement

Forms, features and flows

Every interactive part of the site gets exercised from start to finish. That means submitting each form and confirming the message arrives where it should, with the right information and without landing in spam. It means making a test booking, signing up for the newsletter and, for stores, placing test orders with discount codes, different shipping options and different payment methods, then checking the confirmation emails.

Testers also try the unhappy paths. What happens when someone leaves a required field blank, enters an invalid email or uses an expired discount code? Error messages should be clear and helpful, not cryptic.

Accessibility checks

Testing should include accessibility, ideally with both automated tools and hands-on checks. A few that catch common problems:

  • Navigate the whole site using only the keyboard.
  • Check that every image has appropriate alt text.
  • Confirm form fields are labeled and errors are announced clearly.
  • Verify color contrast on text and buttons.
  • Try key pages with a screen reader.

Performance and technical checks

The team usually reviews page speed on phones, checks that images are compressed and sized properly and confirms caching is configured without interfering with carts or forms. Other technical checks often include:

  • Testing the redirect map so old addresses lead to the right new pages.
  • Looking for broken links and missing pages.
  • Confirming analytics records visits and key actions.
  • Checking that the cookie or consent tool behaves as intended.
  • Making sure backups and security tools are active on the new hosting.

The business’s role in testing

The web team does most of the testing, but the business brings something irreplaceable: knowledge of how customers really behave. Try the site as your customers would. Book the most common appointment, buy the best-selling product or find the information people call about most often. Ask a few staff members to do the same on their own phones. Report problems with the page address, the device and a screenshot if possible.

Advertisement

When testing is complete and the must-fix list is empty, the site is ready to go live. Build Week 7 covers launch itself.

How to Write a Bug Report That Gets Fixed Quickly

When you find a problem during testing, the way you report it determines how fast it gets solved. A developer who can reproduce the issue on the first try can usually fix it quickly. One who has to guess may spend more time searching than fixing. A good report includes:

  1. The page address. Copy it from the browser rather than describing the page.
  2. The device and browser. For example, a particular phone model using its default browser, or a laptop using a specific browser.
  3. What you did. The steps, in order, that led to the problem.
  4. What you expected. What should have happened.
  5. What actually happened. Including any error message, word for word.
  6. A screenshot or short screen recording. These save a great deal of back-and-forth.
  7. Whether it happens every time. Intermittent problems are harder to find, so note how often you saw it.

Put each problem in its own report or line in the shared tracker. Combining several issues in one long message makes it easy for something to be missed.

Sorting the Must-Fix List

Testing almost always produces more findings than anyone expects. Not all of them need to be fixed before launch. A simple three-level sort keeps priorities clear:

  • Must fix before launch: anything that stops a visitor from completing an important task, shows wrong information, breaks on common devices, creates an accessibility barrier on key pages or affects payments, privacy or security.
  • Should fix soon after launch: visual inconsistencies, awkward wording, minor layout issues on less common screen sizes.
  • Ideas for later: new features or improvements that came up during testing but were not part of the original plan.

Agree on the sort together. A wrong phone number may look small, but it belongs firmly in the first group.

A Testing Script for the Business

When you and your staff test the site, a short script ensures the important tasks are covered. Adapt this list to your own business:

  • Find our phone number and address from the homepage in under ten seconds.
  • Find our hours, including any special or seasonal hours.
  • Complete the most common inquiry, booking or purchase from start to finish.
  • Find the answer to the question customers ask us most often.
  • Locate the privacy policy, returns policy or terms.
  • Submit a form with a mistake in it and see whether the error makes sense.
  • Use the site on a phone with one hand while standing up, as many customers will.

Ask each tester to write down anything that made them pause, even if they eventually figured it out. Hesitation is often the first sign of a confusing spot.

Common Testing Blind Spots

  • Testing only while logged in. Administrators often see a different version of the site than visitors do. Test in a private browsing window.
  • Testing only on your own devices. Your newest phone and fast office connection may hide problems customers will meet.
  • Forgetting the emails. Confirmation, notification and password reset emails are part of the site. Check their wording, sender name and whether they arrive at all.
  • Skipping the footer. Footer links, social icons and policy pages are easy to overlook and often point to old addresses.
  • Not retesting fixes. A fix can solve one problem and create another. Recheck each resolved item before it is marked done.

Questions Owners Ask

How long should testing take?

It depends on the size of the site and how many features it has. A simple site may need only a few days, while a store with many products and integrations needs more. Rushing this stage usually costs more time after launch than it saves.

Can we skip testing on older devices?

Your analytics can show which devices and browsers your visitors use. Prioritize those, and do not assume everyone has the newest phone.

Latest stories

View all
Our clients