Software acceptance test plan: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
checklist: | checklist: | ||
# Build new environment | # Build new environment using docker | ||
#* language version & package version | |||
#* system requirement: e.g. CPU & memory usage | |||
# Deploy and run the codes | # Deploy and run the codes | ||
# Testing | # Testing | ||
Revision as of 18:08, 9 April 2018
使用者驗收測試(User Acceptance Test)
Goal -> functional features & non-functional features -> test plain
checklist:
- Build new environment using docker
- language version & package version
- system requirement: e.g. CPU & memory usage
- Deploy and run the codes
- Testing
- Testing by small amount data, large amount data
- Expected or un-expected result
- Validate the dataflow:
- Format of input data & output data
- Definition of column
- Data type of column
- Rows count of data or file size[1]
- Data dependency: If the input data came from previous step, you should check the format of data generated by previous step before executing the process.
- Format of input data & output data
- Progressive update
- Incremental updates: How to apply new data to the current model
- How to use new data to update the model
References