Solution Icon

Solutions

Cutting-edge solutions tailored to everyday issues in the modern digital environment.

Services icon

Services

Innovative tools and services designed to address complex challenges today’s digital landscape.

IT FOR What WE DO MENU

Aerial view of an industrial facility at sunset

Services

Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.

IT FOR HOW WE DO MENU

Aerial view of an industrial facility at sunset

Services

Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.

Ready to clean up your CRM workflow?

Book a CRM Workflow Audit and see where leads, follow-ups, reporting, or disconnected tools can be fixed first.

Insights

Custom Software Testing: What to Require From a Vendor

Before you hire a developer, decide which tests you need, who runs them and what proof you get before each release.

  • Custom Software
  • Buyer Guide
  • Updated November 2026
Dark cover with the words Testing to require from your vendor

Custom software testing should be written into your project before any code starts. Ask the vendor which tests they run, which tests you run, what security and accessibility bar the software must meet, and what proof you get before each release. If those answers are vague, the testing will be too.

What testing should a custom software vendor do?

Testing is not one task. It is a set of checks at different levels, and each one catches a different kind of problem. A vendor quote that says "QA included" tells you very little. Ask which of these are in scope:

  • Unit tests. Small automated checks on single pieces of code. Developers write these as they build.
  • Integration tests. Checks that your software talks correctly to the systems around it, such as your CRM, accounting tool or payment provider.
  • End-to-end tests. A full business task run from start to finish, such as a new order moving from quote to invoice.
  • Regression tests. A repeatable set of checks run before every release, so new work does not break old features.
  • Performance tests. Proof the system holds up with your expected number of users and records.
  • Security tests. Checks against a named standard, not just a scan at the end.
  • Accessibility tests. Checks that people using keyboards, screen readers or zoom can still do the work.
  • User acceptance testing. Your team confirms the software does the job in real conditions.

Not every project needs every level at the same depth. A small internal tool may need light performance testing. A customer portal that takes payments needs all of them. The point is to decide on purpose, in writing.

Why does testing affect the total cost so much?

Because defects get more expensive the later they are found. A bug caught by an automated test costs minutes. The same bug found by a customer after launch can cost support time, data cleanup and trust.

The best-known estimate is old but still useful. A 2002 NIST study put the annual cost of inadequate software testing infrastructure to the US economy at $59.5 billion. It also found that over half of software bugs were not found until "downstream" in development, and estimated that improved testing could remove about $22.2 billion of that cost. Tools have changed since then. The lesson has not: testing early is cheaper than fixing late.

So when you compare quotes, a lower price with thin testing is not always cheaper. Ask each vendor how much of the estimate goes to testing and what that time buys you.

Which tests belong to the vendor and which belong to you?

The vendor owns the technical tests: unit, integration, regression, performance and most security work. They should automate as much of this as makes sense, so it runs on every change.

You own user acceptance. Only your team knows whether the software fits the way work really happens. But you need to prepare for it. That means writing real scenarios ahead of time, naming who will test, and setting aside their hours.

For example, one of our clients, a solar solutions provider, builds task reminders into its Arches workflow automation for every bid. For a setup like that, a good acceptance test is a real bid moving through each stage, with the right person getting the right reminder at the right time. "The reminder works" is not a scenario. A named bid, a named stage and an expected result is.

Agree on test data too. Using copies of real customer data in test systems carries privacy risk. Ask the vendor how they will create realistic test data and who can see it.

How do you set a security testing bar?

Pick a standard and name it in the contract. For web applications, a common choice is the OWASP Application Security Verification Standard (ASVS). Version 5.0.0 was published on 30 May 2025. OWASP lists procurement as one of its intended uses: giving buyers a basis for security verification requirements in contracts.

ASVS groups requirements into levels, so you can match the bar to the risk. An internal tool with low-risk data needs less than a portal that holds customer accounts or payments. Ask the vendor which level they propose, why, and how they will show you the results.

If your software connects to other systems, test those connections hard. We cover that in our guide to partner API acceptance tests.

Should accessibility be part of testing?

Yes, and it is far cheaper to build in than to fix later. The usual reference is the Web Content Accessibility Guidelines (WCAG) 2.2 from W3C. It defines three conformance levels: A, AA and AAA. Many organizations use AA as their target, but the right target depends on your users and your obligations, so confirm it with your own advisers.

Ask the vendor to test with automated tools and by hand. Automated tools catch some issues, such as missing labels. Manual checks, like using the whole app with only a keyboard, catch problems tools miss.

What proof should you get before each release?

Do not accept "it's tested" on trust. Ask for a short release pack each time:

  • The test plan for the release and what changed since the last one.
  • Results from the automated test run, with any failures explained.
  • A list of known defects, each with a severity and a fix plan.
  • Your team's signed user acceptance results.
  • A rollback plan if something goes wrong after launch.
  • Proof that backups restore, for any release that touches data. See our guide on database restore testing.

What should the contract say about defects?

Most disputes come from defects nobody defined. Agree on these points before work starts:

  • Severity levels. What counts as critical, major and minor, with an example of each.
  • Response times. How fast each severity gets a fix or a workaround.
  • Warranty period. How long after launch the vendor fixes defects at no extra cost.
  • Exit criteria. The rule for go-live, such as no open critical defects and signed acceptance tests.
  • Ownership of tests. Automated tests are part of what you pay for. Make sure you keep them if you change vendors.

That last point matters more than most buyers think. A good regression suite makes every future change safer, whoever does the work.

Frequently asked questions

How much of a custom software budget should go to testing?

There is no single right share. It depends on risk, integrations and how much is automated. Ask each vendor to show the testing hours in their estimate and explain what those hours cover, then compare like for like.

What is user acceptance testing?

User acceptance testing is when your own team checks that the software does the job in real conditions, using real scenarios. It is usually the last step before go-live, and you, not the vendor, sign it off.

Is automated testing enough on its own?

No. Automated tests are fast and repeatable, so they suit regression and integration checks. You still need people for acceptance testing, accessibility checks by hand and judging whether the workflow makes sense.

Should I keep the test suite if I switch vendors?

Yes. Your contract should say the automated tests, test data scripts and test plans belong to you. A new vendor can use them to change the software without breaking what already works.

Sources

  1. NIST: The Economic Impacts of Inadequate Infrastructure for Software Testing, Planning Report 02-3 (2002)
  2. OWASP Application Security Verification Standard (ASVS)
  3. W3C: Web Content Accessibility Guidelines (WCAG) 2.2

Planning custom software and want testing done right?

We build custom software with automated tests, clear acceptance steps and release proof you can check, so you know what you are getting before it goes live.

See custom development services

BUSINESS SYSTEMS

SOFTWARE

AI

INTEGRATIONS

Build, Improve, or Connect the Systems Your Business Depends On.

Whether you need custom software, CRM, ERP, AI, automation, integrations, or modernization, tell us what you’re trying to improve. We’ll review your requirements and recommend the most practical next step.

300+

Software projects delivered

37+

Enterprise apps built

150+

delivery team members

★★★★★ 4.7 on Google · 20 reviewsU.S.-led since 200721 awards & certifications →
Client results
BMG: cut the time lost on follow-ups by 70% with our CRM.
Utah Dental Association: convention registration streamlined from months to one month.

Tell Us About Your Project

No sales pressure. Tell us what you’re trying to build, improve, integrate, automate, or replace. We’ll review your answers and come back with a clear recommendation within 1 business day.

Prefer to talk now? Call +1 (801) 259-4800 or book a free 30-minute review.

© 2026 Hexagon IT Solutions. All rights reserved.