Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Engineering

Who signs off application acceptance testing, on what criteria and with what reservations?

In brief

Application acceptance testing brings together the checks at the end of which the sponsor of an application declares that it accepts it, rejects it or accepts it with reservations. Management Square indicates here what it must decide (signatory, criteria, handling of defects by severity), describes the stages, from internal testing to regular service verification, and the place of acceptance in an agile approach.

Page contents

Application acceptance testing is the set of checks at the end of which whoever commissioned an application declares that they accept it, reject it or accept it with reservations. The term belongs to the usage of IT projects: its exact content is set in each contract or, for an in-house build, in each acceptance test plan.

Acceptance testing is therefore prepared like a decision. Four points need deciding before the first test campaign: who signs off acceptance, on what criteria, what becomes of a defect according to its severity, and in which cases you reject or accept with reservations. The usual stages then organise the work: internal testing, business acceptance testing, then fitness verification and regular service verification when the contract provides for them. In an agile approach, the decision remains and is spread out.

A named person signs off application acceptance

Acceptance is a formal act: someone signs. Common usage gives this role to the project owner (maîtrise d’ouvrage), the department on whose behalf the application is built. The designation is made by name, with a deputy: the users who run the test cases build the case for the decision, business-side project support may prepare it, the signatory takes it.

The public ISTQB glossary (glossary.istqb.org, read on 12 November 2026) defines acceptance testing as “a test level that focuses on determining whether to accept the system”. It describes types of it: user acceptance testing, performed “to determine if intended users accept the system”, and operational acceptance testing, which seeks to determine whether the organisation responsible for running the system can accept it.

Operations therefore have their part: an application judged compliant by the business, which nobody knows how to back up or restart, is not ready.

Criteria fixed before the first campaign

Acceptance testing compares a result with a reference. That reference is the requirements specification, or the backlog, in a dated version, with its acceptance criteria; writing them is covered in our article on an application’s requirements specification. An expectation that does not appear there and is discovered during acceptance testing is a change request, to be examined as such.

The acceptance test plan sets the conditions of the act itself:

  • the entry conditions: the builder’s tests completed and results passed on, known defects listed, environment and data ready;
  • the cases to run, linked to the requirements, and the people released to run them;
  • the exit conditions: the number of open defects tolerated for each severity level;
  • the quality requirements (load, security, recovery) for which evidence is expected, and in what form.

These entry and exit criteria, stage by stage, appear in the test strategy built by our software quality offering.

A defect is classified by severity before it weighs on the decision

Each discrepancy found is recorded, reproduced, then classified. The scale below is one possible convention, to be adapted and written down before acceptance testing.

Severity Proposed definition Effect on the decision
Blocking A function needed for the business is unusable, or a result is wrong, with no workaround No acceptance while it remains open
Major The function is degraded; a workaround exists, at the cost of effort for users Acceptance possible with a reservation, if the workaround is written down and the fix dated
Minor Defect with no effect on the result: label, presentation, convenience Acceptance possible; fix scheduled

Take, as an assumption, a network of driving schools testing its lesson booking application for acceptance. A wrong price for twenty-hour packages is blocking. Being unable to print two appointment notices in a row, worked around by reopening the screen, is major. A spelling mistake in a label is minor.

The requester proposes the severity, the builder may challenge it, and a body designated in advance decides. Any downgrading is traced, with its reason.

The decision then takes one of three forms: acceptance; acceptance with reservations, each assigned, dated and lifted by a finding of the signatory; rejection, or postponement until a new submission.

The effects of the decision are settled in the contract, with the lawyers. Does acceptance trigger a payment? Does it start a warranty period, and which one? Does a production release before any decision count as acceptance? What happens if the sponsor does not decide within the agreed time? These questions call for a written answer before the first campaign.

Internal testing, business acceptance testing, fitness and regular service verification

The names of the stages vary from one project to another. Internal testing is carried out by the builder before submitting its delivery: it runs its own tests and passes on the results. The lower levels of the test pyramid have then been passed.

Business acceptance testing is carried out by the sponsor, with users, on an environment close to production and with representative data. It replays complete user journeys and grounds the decision.

Fitness verification (vérification d’aptitude, VA) and regular service verification (vérification de service régulier, VSR), abbreviations in common use, are terms from French public procurement. The general administrative terms and conditions for public contracts for information and communication technologies (CCAG-TIC), approved by an order of 30 March 2021 and read in the archive of 8 November 2026 of the DILA’s LEGI database, make them in Article 32 the two stages of qualitative verification. The first establishes that the services have “the technical characteristics that make them fit to perform the functions specified in the contract-specific documents” (our translation). The second begins if the first is positive: it establishes that the services are capable of providing “regular service under normal operating conditions” (our translation). In a contract that refers to these terms and conditions without derogating from them, regularity is observed for thirty days, the buyer then pronounces admission, postponement, admission with a price reduction or rejection (Articles 33 and 34), and without a decision notified within seven days following regular service verification, the services are deemed admitted (Article 33.2.2).

These terms and conditions apply only to contracts that expressly refer to them, and those contracts may derogate from them (Article 1 of the order and Article 1 of the terms and conditions). Their preamble describes them as “not suited” to contracts concluded by private buyers. A private contract that takes up the words VA and VSR must therefore write down their content, duration and consequences itself.

In an agile approach, acceptance is spread across increments

The term acceptance testing does not appear in the Scrum Guide (November 2020 version, read on scrumguides.org on 12 November 2026). The Definition of Done is described there as “a formal description of the state of the Increment when it meets the quality measures required for the product”. An item that does not meet it cannot be released or even presented at the Sprint Review, which the Guide describes as a working session with stakeholders without making it, in our reading, an act of acceptance.

Acceptance can then sit at two levels. Each backlog item is accepted by the product owner against its criteria, which can be written as behaviour-driven development scenarios. Each production release keeps an explicit decision: non-regression, carried by automated tests, quality requirements, agreement of operations. Our page custom software development describes this delivery in increments.

With a supplier, acceptance of each batch or increment is defined in the contract, according to the engagement model chosen (fixed fee or time and materials).

On a project in progress, preparation can begin with the last document: the acceptance certificate, drafted blank. Who signs it, what decisions it proposes, what defect severity prevents signature, where reservations are recorded: a box left empty signals a decision that the acceptance test plan has not yet taken.

FAQ

Frequently asked questions

Another question? Ask us

What is the difference between acceptance testing and testing?

Testing looks for defects, at every level and throughout the build. Acceptance is the stage at which the sponsor decides whether or not to accept what is delivered to it: it relies on tests, called acceptance tests, and ends with a formal act, the acceptance certificate. The ISTQB glossary defines acceptance testing as a test level that focuses on determining whether to accept the system.

Who signs the acceptance certificate?

In practice, a person designated in advance by the department on whose behalf the application is built, called the project owner (maîtrise d'ouvrage) in projects. The users who run the test cases and the business-side project support prepare the decision without taking it. The opinion of operations, who will have to run the application, is gathered before signature.

Can you go live with reservations?

Yes, when the remaining defects allow business to continue and each reservation is assigned, dated and checked when it is lifted. A blocking defect, which makes a necessary function unusable or falsifies a result with no workaround, stands in the way of acceptance. Thresholds by severity are written before acceptance testing; the effects of acceptance with reservations on payment or on a warranty are read in the contract, with a lawyer.

What do VA and VSR mean?

In practice, VA stands for vérification d'aptitude (fitness verification) and VSR for vérification de service régulier (regular service verification), terms that the general administrative terms and conditions for French public contracts for information and communication technologies (order of 30 March 2021) write out in full. Its Article 32 makes them the two stages of qualitative verification: the first establishes fitness to perform the specified functions; the second observes the regularity of service for thirty days. These rules apply only to contracts that refer to these terms and conditions, which may derogate from them; a private contract that uses these terms must set their content and duration itself.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.