INADEQUATE DOCUMENTATION
Jump to navigation
Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
................................................................................................................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:
- DOCUMENT THE TESTWARE: Document the automation scripts and the test data
- DESIGN FOR REUSE: Design reusable testware
Other useful patterns:
- SET STANDARDS: Set and follow standards for the automation artefacts
................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues