INADEQUATE DOCUMENTATION

From Test Automation Patterns
Revision as of 08:23, 5 April 2018 by Cathal (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues

Issue Summary


Test automation testware (scripts data etc.) are not adequately documented

Category


Process

Examples


Test scripts are not documented at all or not adequately, so they cannot be found (no reuse) or nobody knows what they actually do.
Available data is not documented so it cannot be reused.
Documentation is missing about the kind of data and / or where to find it or where to store it.
There is no overview of the automation "regime" - where various artefacts are stored, the aims and objectives of the automation, etc.

Questions


Who creates the scripts? Who maintains them?
Who creates the data? Who maintains it?
Who uses the data or the scripts?
Are there standards? Are they used?

Resolving Patterns


Most recommended:


Other useful patterns:


................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues