A company that writes the steps down first
Testiform LTD tests the journeys a website is used through - the ones that end in an account, a booking or a payment - before it goes live and after it changes. The output is a document somebody else can act on, not an opinion about how the site feels.
What the work is
A website that has just been built, or has just been changed, has a set of routes through it that matter more than the rest: signing up, getting back in, finding something, filling a form in, holding a slot, paying. Those routes are the ones a customer meets first and the ones that cost something when they misbehave.
The work is to take each of those routes, step by step, on an environment the customer approves, and to compare what happens with what the site says should happen. Where the two differ, the difference is written up in a form a developer can reproduce from, with a recording attached to it.
That is the whole of it. There is no consultancy layered on top, no dashboard to log into and no monthly retainer to sign. A pass is ordered, run and delivered, and a retest is ordered separately if and when there is something to retest.
Four habits the work is built on
None of these are unusual in testing. They are written down here because they are the things a customer is entitled to check a supplier actually does.
The case is written before it is run
A step with no written expectation cannot fail, it can only feel wrong. So every step is written down first, with the result it has to produce, and the run is a comparison rather than a look around.
Everything is recorded, not only the failures
A pass that records only what broke cannot be repeated and cannot be compared with the next one. The full case list goes to the customer, so a second pass measures against the first instead of starting again.
A finding is written for the person who has to fix it
Steps in order, the environment and browser named, expected beside actual, and a recording of the whole thing in one take. A developer should be able to reproduce an entry without asking a question.
Priority describes the journey, not the fix
The scale is published with the report. It says what the finding does to the customer going through the journey, and says nothing about how long anybody thinks the repair will take.
Four things that are not on offer
No sign-off on quality
No certificate, no badge and no mark out of ten. A report says what was run and what it found. Anything beyond that would be a claim about the parts that were not run.
No testing without authority
A website is exercised only where the customer owns it or is authorised in writing to submit it. That is confirmed in the request and again in the order.
No live payments, ever
Checkout is exercised in the payment provider’s sandbox with its published test cards. No live card is charged and no live refund is issued to make a point.
No customer work on show
Reports belong to the people who ordered them. Nothing a customer has paid for appears on this site, in a portfolio or in an example.
Details
Getting in touch
Email is the way in. Enquiries, scope questions, a report that needs explaining and a complaint all go to the same address, and none of them are routed through a form that hides where they land.
What testing needs from a customer is an address, a list of journeys and an environment. All three are better written down than said once and remembered differently by two people afterwards, which is why the whole arrangement runs on writing.
Access details never go by ordinary email. Once a scope is agreed, credentials come through a one-time secret link or a share from your own password manager, and they are deleted when the pass is finished.
Test your website before launch
The request form asks for the address, the journeys that matter and what there is to test against. Nothing else, and never a password.