In keyword-driven test automation, keywords should represent business-readable, reusable actions at an appropriate level of abstraction — not overly granular implementation steps. For a standard ATM cash withdrawal, the minimal set of keywords covers authentication (Login customer), the action under test (withdraw cash), and a verification step to confirm the outcome (verify balance). This gives testers a check that the withdrawal actually occurred and the balance reflects the transaction, which is essential for a valid keyword-driven test. Options that omit login or verification are incomplete, while a more granular breakdown (accept withdrawal request, disburse cash, update balance) represents implementation detail rather than the appropriate keyword abstraction level for this user story.
Community Discussion