Testing a document management system: documents, permissions, search and evidential value
A document management system stores contracts, invoices and HR files. Users trust it to find the right document, in the right version, and to hide it from those who must not see it.
- Permissions are the first risk: a document visible to the wrong person is a data leak.
- Search must find the right document, including after scanning and text recognition.
- Versions are never lost: history, restore, locking.
- Document management is not evidential archiving: the latter follows specific standards (NF Z42-013 in France).
Oussama Belakhdar, QA architect and founder of AutomationDataCamp, has worked on testing projects for document management and digitisation. This page details our priority checks on a document management system or an archiving system. Our clients remain anonymous.
What do the document management and archiving figures say?
Figures published by the organisations cited, not results of our own engagements.
Why is document management harder to test than it looks?
- Permissions combine users, groups, folders, metadata and inheritance: the number of combinations quickly exceeds what can be checked by hand.
- Documents arrive through every channel (scanning, e-mail, bulk import, API, business connectors), in very varied formats and quality.
- Text recognition (OCR) is never perfect: its quality depends on the scan, the language and the layout.
- Volumes grow for years: a search that is fast on a thousand documents can become slow on millions.
Cases to cover first in a document management system
- Import: accepted formats, large, corrupted or password-protected files, duplicates.
- OCR and indexing: text extracted from a skewed or low-resolution scan, accents, tables, multi-page documents.
- Search: by metadata, full text, with typos, results filtered by the user's permissions.
- Permissions: read, edit, delete by role, inheritance between folders, direct access through a shared link.
- Versions: creation, comparison, restore, locking during editing.
- Life cycle: retention periods, legal hold, logged destruction.
Evidential value, eIDAS, GDPR: the obligations to cover
Archiving with evidential value: NF Z42-013 and ISO 14641. The French standard NF Z42-013 (international equivalent: ISO 14641) sets the requirements for an electronic archiving system designed to guarantee document integrity over time; a standard document management system does not have that value by nature. Tests target the guarantees expected from such a system: a fingerprint for each document on intake, an event log, integrity checks, retrieval identical to the original.
Reliable copies: Article 1379 of the French Civil Code. A reliable copy has the same evidential force as the original. Decree No. 2016-1673 of 5 December 2016 specifies the electronic copy process that allows that reliability to be presumed: identification information for the copy, including its creation date, and integrity guaranteed by an electronic fingerprint. The NF Z42-026 standard covers faithful digitisation. Tests check that this information is produced and kept for every scan.
eIDAS: signatures, seals and timestamps. Regulation (EU) No 910/2014, amended by Regulation (EU) 2024/1183, governs electronic signatures, seals and timestamps; the 2024 revision notably adds qualified electronic archiving to the trust services. When a document management system checks or applies signatures, tests cover valid, expired and revoked signatures, and a document changed after signing.
GDPR: retention periods. Personal data must not be kept longer than necessary (Article 5 of the GDPR); the French CNIL publishes guidance by type of data. Each retention rule becomes a test: when it expires, the document is destroyed or archived, and the operation is logged.
An example test case: a file that will still open decades from now. For long-term archiving, documents are often converted to PDF/A (ISO 19005), a subset of PDF that excludes what would prevent faithful rendering later: fonts must be embedded, encryption is not allowed and the file cannot depend on external content. veraPDF, an open source validator built for digital preservation, covers every PDF/A part and conformance level. A typical test feeds the conversion chain a deliberately difficult corpus (a Word file using a font installed only on the author's machine, a password-protected PDF, a scan with transparency, a spreadsheet with external links), validates every output with veraPDF against the targeted level, for example PDF/A-2b, and checks that the fingerprint calculated on intake still matches on retrieval. A file the system reports as archived must either pass validation or be rejected with an explicit reason, never stored silently as non-compliant.
Testing OCR and search at realistic volumes
The quality of a document management system often comes down to one simple question: does the user find the document they are looking for? We build a representative corpus of fictitious documents (scanned invoices, contracts, handwritten forms, poor-quality documents) with the expected text and metadata for each. Recognition rate and search relevance are then measured in every release instead of being judged by eye.
Search performance is tested on an index of realistic size, generated by script: a response time measured on a few thousand documents says nothing about what will happen after five years of use.
How do we organise testing for a document management system?
- Start from leaks and losses. A document visible to the wrong person or impossible to find costs more than a usability defect: permissions, search and integrity come first.
- Test permissions as a matrix. Role × folder × action combinations are generated and checked with API tests; Playwright covers import, search and sharing, k6 covers search under load, all attached to your continuous integration.
- A fictitious but realistic corpus. Documents generated for testing, never real personnel files or contracts.
- AI, with a review. An assistant helps produce corpus documents and the permission matrix. Each proposal is checked using our 7-question checklist. For an example, read our case study: from a PDF specification to Playwright tests.
Where should you start?
A practical first step is often the permission matrix: it quickly reveals combinations that have never been tested.
A QA audit reviews your application: a written assessment, a test strategy adapted to your industry and a costed action plan, in 5 days, for €1,000 excl. VAT as a fixed fee. Delivered remotely, in English or French, for companies in the US, the UK, Canada, Australia, Europe, the Gulf and the Nordics. The first scoping session is free.
See the QA audit at €1,000 excl. VAT
Frequently asked questions about document management testing
Does a document management system have evidential value?
Not by nature. Evidential value comes from an electronic archiving system compliant with NF Z42-013 (ISO 14641). A document management system can feed such a system, and that link is tested.
What should be tested first in a document management system?
Access permissions (including direct access by link), search, version management, and retention and deletion rules. Permissions lend themselves well to automated API tests, role by role.
How do you test OCR quality?
With a corpus of documents whose expected text is known: the extracted text is compared with the reference text, document by document, and the error rate is tracked in every release. Difficult documents (skewed scans, low resolution, handwriting) are part of the corpus.
How do you test retention periods?
By creating fictitious documents dated in the past, or by controlling the clock of the test environment, then checking that on expiry each document is destroyed or archived according to its rule, that a legal hold blocks destruction, and that every action is logged.
How much does a QA audit cost at AutomationDataCamp?
The QA audit and diagnosis costs €1,000 excl. VAT as a fixed fee, over 5 days: a written assessment, a test strategy and a costed action plan. The first scoping session is free.
Other industries: Healthcare · E-invoicing · Finance · Blockchain · Logistics · E-commerce. All industries.
Page signed by Oussama Belakhdar, written with the help of AI. Regulatory references link to the official sources above; they are not legal advice.
Related articles

AI & ML for test automation
What AI concretely changes in test automation.
Read more : AI and ML for test automation
Integrating Automation into CI/CD
Jenkins, GitLab CI, GitHub Actions — practical examples.
Read more : Integrating Automation into CI/CD