AI GxP validation for regulated life sciences
Test Automation

Automating IQ: Verifying an Installation When There Is No User Interface

OQ and PQ automation gets all the attention because there is a screen to click. IQ is mostly files, versions, services and permissions, which is why it is still done by hand. It does not have to be.

Cybroscape Technologies4 min read

Key takeaway

OQ and PQ automation gets all the attention because there is a screen to click. IQ is mostly files, versions, services and permissions, which is why it is still done by hand. It does not have to be.

Automation discussions default to OQ and PQ because there is a screen to click and a tool that clicks it. IQ gets left behind — still a person with a checklist, reading version strings off a terminal and pasting them into a Word table.

Which is odd, because IQ is the most automatable of the three. It is almost entirely a set of factual assertions about a machine.

What IQ actually asks

Strip away the formatting and installation qualification asks a short list of closed questions:

  • Is the software present, at the version the specification names?
  • Are the files the ones the vendor shipped — checksums matching, nothing added?
  • Are the services running, and set to start on boot?
  • Is the operating system, runtime and database at a supported version?
  • Are directories, permissions and ownership as specified?
  • Are the configured connections — database, storage, identity — pointing where they should?
  • Is there enough of what the system needs: memory, disk, licences?

Every one of those has a definite answer that a machine can read, and no judgement in it. The reason it is still manual is not difficulty. It is that the tools were built to drive browsers.

Reaching the host without handing over a shell

The obvious way to check a file version is to run a command, and we have argued at length against giving a test engine that ability. The two are reconcilable: the engine needs named checks against a host, not arbitrary execution on it.

So the step types are specific rather than general:

  • File check — exists, size, checksum, modified time, permissions, owner.
  • Version check — read a version from a named source and compare against an expected value.
  • Service check — named service, running state, startup mode.
  • Resource check — free disk on a named mount, available memory, a named licence count.
  • Connection check — a named endpoint is reachable and identifies itself as expected.

Each takes parameters and returns a fact. None of them can be asked to do anything else. The same vocabulary works whether the target is the local machine, a host over SSH, or a container — the connection method is configuration, not a new class of step.

The failure that proves it is working

The first time an automated IQ fails on a real environment is the moment it earns its place. When we ran the full chain end to end on our own test estate, the IQ failed — a genuine mismatch between the specified and installed state, found in seconds rather than by a person reading a version string at the end of a long day.

It raised a deviation, which is exactly what should have happened. A failing automated test is not an inconvenience; it is the system doing the one job you bought it for. A tool that has never failed on your estate has not been tested, it has been demonstrated.

Where a person is still better

Two parts of IQ resist automation, and it is worth conceding them rather than pretending otherwise.

  • Physical verification. Cabling, labelling, rack location, environmental conditions. If it is a fact about the room rather than the machine, somebody has to look.
  • Documentation review. Confirming the vendor supplied what the contract says, that the manuals are the right revision, that the supplier qualification is current. See supplier qualification.

A realistic split on a typical system is most of the machine-readable checks automated and a short manual annex for the rest. That is still a large reduction in the part of IQ that is pure transcription — and transcription is where the errors were.

Where to go next

Explore Cybroscape GxP Copilot for AI-native validation, Cybroscape TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.

ELN
LIMS
MES
ERP
CompleteAttributableUnchanged
Each system can be validated and the data can still break between them. Every handoff needs its own check that the data arrived complete, attributable and unchanged.
See it on your own systemBring a URS or a system. We run GxP Copilot against it live on the call.
automated iqinstallation qualification automationiq oq pq automationinfrastructure qualificationgxp installation verification

Keep reading

All articles
Test AutomationAutomating IQ/OQ/PQ Protocols: What Works, What Fails, and What Inspectors ExpectWhere test automation adds genuine value in IQ/OQ/PQ execution, where it introduces new compliance risk, and how to build an audit-ready automated protocol record. · 5 min readTest AutomationGxP Test Automation: The Complete Technical Guide Under CSA in 2026How to build a GxP test automation strategy under Computer Software Assurance: what to automate, what not to, how to document it, and how to keep it defensible under inspection. · 6 min readTest AutomationGxP Test Automation and 21 CFR Part 11: The Audit Trail Requirements That Most Teams MissThe Part 11 requirements that apply specifically to automated test execution (audit trail, e-signature, result attribution, and data integrity) with a defensible record structure. · 5 min readTest Automation7 Best GxP Validation Test Automation Tools (2026): CSA, UI, API & Equipment AdaptersA technical comparison of GxP test automation tools, including Cybroscape GxP Copilot (12 closed-vocabulary adapters across Web, API, SQL, OPC UA & data loggers), Tricentis Tosca, Vera, Playwright and Selenium, scored on 21 CFR Part 11 evidence, maintenance cost, and FDA CSA alignment. · 6 min readTest AutomationYour Test Automation Tool Is Also a GxP SystemIf a tool produces the evidence that another system is validated, the tool is in scope. The recursive problem nobody wants, and the proportionate way through it. · 4 min readTest AutomationRe-Running a Protocol After a Change: How to Scope Regression HonestlyAutomation makes re-running everything cheap, which is exactly why teams stop thinking about what actually needed re-running. Scoping regression on risk rather than on convenience. · 4 min readTest AutomationRisk-Based Test Automation in GxP: How to Build a Defensible Automation StrategyHow to apply per-requirement risk scores to drive test automation decisions: what gets scripted automation, what gets exploratory execution, and what borrows vendor evidence. · 4 min readTest AutomationWhen Not to Automate a Validation ProtocolThe honest counterweight to every automation pitch. Six situations where a scripted manual execution is the better answer, and how to say so in a way that survives review. · 4 min read

Bring a system. We'll show you the package.

Book a demo, or ask a validation lead a quick question on WhatsApp.

  • We reply within one business day
  • We run your URS live on the call
  • You get a clear plan for your system
Chat on WhatsApp

Book a demo

Four fields. The right specialist replies within one business day.

Your details stay private. We never share them.