Software acceptance test plan
Jump to navigation
Jump to search
使用者驗收測試(User Acceptance Test, UAT)
Goal -> functional features & non-functional features -> test plain
Checklist[edit]
- Build new environment using docker
- Language Interpreter 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
[edit]
References:
Related articles:
- What is an acceptance test plan? - Original Software
- Introduction to pipelines and jobs | GitLab
- Functional testing - Wikipedia function test (功能測試)
- 軟體測試報告 (Software Testing Report, STR) 軟體/系統測試報告(STR)文件下載-Kris專案管理學院