Skip to content
TACTICALOEM / ODM TACTICAL APPAREL
ENEnglish

Field Testing

What a Fabric Test Report Tells You

A test report is a record that a specific sample was assessed by a specific method on a specific day. It is evidence, not proof, and it describes fabric rather than a garment. This is how to read one properly.

Publication date to be confirmed · 10 min read

Buyers are often handed a fabric test report as if it were a guarantee. It is not. A report is a record that a particular sample was assessed by a particular method on a particular date. Everything that makes it useful or useless lies in those three details.

Reports are nonetheless valuable, and a buyer who can read one has a real advantage in a sourcing conversation. This is how to read them, what they cannot tell you, and how to make reports from different suppliers comparable.

The header matters more than the results

Before looking at any result, read the identification block. It should tell you the laboratory, the sample identity, the date, the method used and the standard version, and often the conditioning and the number of specimens.

Four of those deserve specific attention.

Sample identity. Is this a report on the fabric you are being offered, or on a generic sample of the same family? A report that does not reference a construction and a lot cannot be tied to your order.

Method and version. Test methods change between revisions, and results from different revisions are not directly comparable. A report that names the method but not the version is only partially useful.

Conditioning. Textile properties, particularly those involving moisture, depend on how the sample was conditioned before testing. Standard conditioning is normal, but it does not describe a garment that has been worn in the rain.

Direction and specimens. Woven fabrics behave differently along and across the grain, so direction should be stated. The number of specimens matters too, because a result from a single specimen says much less than a result averaged over many.

If any of those is missing, the report is still a data point but it is not a specification you can hold a supplier to.

What the common tests actually measure

Test What it measures What it does not tell you
Tensile strength Force to break a strip pulled in one direction Behaviour under multi-directional load or wear
Tear strength Force to propagate an existing tear Whether a tear will start
Abrasion resistance Material loss under a defined rubbing action Real abrasion from ground, gear or vehicle contact
Colour fastness Shade change or transfer under a defined exposure Long-term appearance across a garment's mixed components
Dimensional stability Change in size after a specified wash cycle Behaviour under the user's actual laundry regime
Water repellency Surface wetting behaviour under a defined spray or pressure Water resistance of the finished garment including seams
Moisture management Liquid transport behaviour in a defined test setup Drying rate in the conditions the wearer experiences

Two points are worth drawing out.

The first is the difference between abrasion and tear. Abrasion resistance describes material loss from rubbing, while tear strength describes resistance to a tear that has already started. They are different mechanisms and a fabric can be good at one and poor at the other.

The second is the difference between surface repellency and liquid resistance. A spray rating describes how a fabric surface sheds water; hydrostatic resistance describes pressure required for water to pass through. A garment can have excellent surface repellency and still leak at the seams, because seams are not covered by the fabric test.

Why a true report can still mislead

A test report can be entirely accurate and still lead you to a wrong decision. The usual mechanisms are these.

Fabric is not a garment. A report describes a flat sample. Assembly, seams, stitch perforation, reinforcements and the way the garment is worn all change performance. A waterproof fabric with excellent results can produce a leaking waterproof tactical shell if the seam construction is wrong.

Unwashed is not washed. Many properties change after laundering, and the after-wash columns are the ones that predict field behaviour. If the report shows only new-state results, ask for after-wash data.

Best sample is not production. A report may have been produced on a laboratory-prepared sample or on a trial lot. Unless the report identifies the lot that your order comes from, it describes a capability rather than your goods.

One lot is not a supply. A single passing report describes one lot. Consistency across lots is a process question, which is why batch consistency is a separate requirement from any individual test result.

A stressed sample is not the field. Laboratory tests apply defined forces in defined ways, while real wear combines abrasion, moisture, UV, laundering and contamination in ways no single test reproduces.

This is not an argument against testing. It is an argument for treating a report as one input and for testing your own garment, not only the fabric.

How to make reports comparable

The practical way to get value from fabric testing is to standardise what you ask for, so that a report from one supplier can be read against a report from another.

Write the requirement so that each item names the property, the method and the state of the sample. Ask for results on both new and laundered samples where the property can change with washing. Ask for direction to be stated, for the number of specimens, and for the sample identity to reference the construction and lot.

Keep the fabric itself as well: a retained physical standard, stored and labelled, lets you re-test the same material later and compare a new lot against it, and it captures colour and hand, which no report describes well.

Finally, decide what you will do with a result. A test result is only actionable if the specification says which properties are requirements, what level is acceptable, and what happens when a lot is outside it. That decision belongs in the specification and in your quality control process, not in a conversation after the report arrives.

In wet-weather tactical clothing intended for wet weather use, testing should include the assembled garment as well as the fabric, because the failure modes that matter — seam leakage, wicking at the hem, water entering at openings — are construction outcomes. For hot-weather garments, after-wash drying behaviour usually tells you more about the wearer's experience than any new-state measurement.

Questions to ask when a report arrives

  • What exactly was the sample, and is it the construction we are being offered?
  • Which method and which version of it were used?
  • Was the sample new or laundered, and what were the wash conditions?
  • In which direction were the specimens taken?
  • How many specimens were tested, and what was the spread of results?
  • Does the report describe a lot, a trial, or a laboratory-prepared sample?
  • What happens if a future lot falls outside these results?

The last question is the one that converts a document into a control. A supplier who can answer it has a process. A supplier who cannot has a certificate.

FAQ

Does a passing test report guarantee the fabric will perform?

No. It records that a sample met the stated criteria under the stated method. It does not cover the assembled garment, real wear conditions, or the consistency of future lots. Use it to compare candidates and to set requirements, not as a substitute for your own evaluation.

Why do the numbers look different from another supplier's?

Differences usually come from sample identity, method, method version, conditioning or the state of the sample rather than from the fabric itself. Ask for the header details before comparing values, and if the report does not provide them, treat the comparison as indicative.

Can I ask for testing on the finished garment?

You can, and for several properties you should, because garment-level testing is more relevant to seam durability, rain resistance and comfort than fabric-level testing. It is slower and more expensive, so select the properties where the assembly decides the outcome.

What should I do with the report after I receive it?

File it with the retained fabric sample and the order record, and reference it in your specification. Then check incoming lots against the retained sample. A report that is not connected to a retained standard and an inspection step has no effect on what you actually receive, which is ultimately what colour and quality control is about.

FAQ

Frequently asked questions

Does a passing test report guarantee the fabric will perform?

No. It records that a sample met the stated criteria under the stated method. It does not cover the assembled garment, real wear conditions, or the consistency of future lots. Use it to compare candidates and to set requirements, not as a substitute for your own evaluation.

Why do the numbers look different from another supplier's?

Differences usually come from sample identity, method, method version, conditioning or the state of the sample rather than from the fabric itself. Ask for the header details before comparing values, and if the report does not provide them, treat the comparison as indicative.

Can I ask for testing on the finished garment?

You can, and for several properties you should, because garment-level testing is more relevant to seam durability, rain resistance and comfort than fabric-level testing. It is slower and more expensive, so select the properties where the assembly decides the outcome.

What should I do with the report after I receive it?

File it with the retained fabric sample and the order record, and reference it in your specification. Then check incoming lots against the retained sample. A report that is not connected to a retained standard and an inspection step has no effect on what you actually receive, which is ultimately what [colour and quality control](/insights/how-to-control-color-between-production-batches/) is about.

Specifying a programme now?

Send the tech pack, reference sample or product requirement. We review it and come back with the specification gaps and a development plan.