What is keyword-driven testing?
A way of writing tests as sequences of named actions with arguments, such as open a page, type into a field, read a table, compare two values, so that a tester composes a test without writing code and the engine supplies the implementation of each keyword. Here the keywords are nodes on a canvas and entries in an 81-keyword catalogue, each with a declared argument schema.
Is this robotic process automation?
In part. The RPA nodes capture a page as a record, fill a form from a record, verify a page against one and branch on a decision table, and a recording can run as a self-healing bot on a schedule. It is built for testing and for small browser jobs, not as a replacement for an enterprise RPA platform.
Can I import my n8n workflows?
Yes, as a starting point: an exported n8n workflow is imported with unsupported node types reported and embedded secrets stripped, up to sixty nodes. You then replace what did not map and add credentials from the vault.
What happens when a step fails at three in the morning?
The failure is classified from a table. A retryable step is retried only if it is idempotent, compensation runs in reverse where it is defined, and the item lands on the exception desk with its screenshot and trace, a due time and, where set, an escalation. A human input step that nobody answers fails at its due time and opens an exception.
Do my credentials leave Dokimore?
Connector nodes use credentials from your vault, encrypted at rest and referenced by name; each connector verifies the account before it runs, and outbound calls go only to allow-listed hosts. Dokimore holds no shared integration account on your behalf.