Software acceptance test plan: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
使用者驗收測試(User Acceptance Test) | 使用者驗收測試(User Acceptance Test, UAT) | ||
Goal -> functional features & non-functional features -> test plain | Goal -> functional features & non-functional features -> test plain | ||
== Checklist == | |||
# Build new environment | # Build new environment using docker | ||
#* Language Interpreter version & package version | |||
#* System requirement: e.g. CPU & memory usage | |||
# Deploy and run the codes | # Deploy and run the codes | ||
# Testing | # Testing | ||
#* Testing by small amount data, large amount data | #* Testing by small amount data, large amount data | ||
#* Expected or un-expected result | #* Expected or un-expected result | ||
#* Validate the | #* Validate the [https://en.wikipedia.org/wiki/Dataflow dataflow]: | ||
#** Format of input data & output data | #** Format of input data & output data | ||
#*** Definition of column | #*** Definition of column | ||
| Line 20: | Line 22: | ||
#* How to use new data to update the model | #* How to use new data to update the model | ||
References | == References & related articles == | ||
References: | |||
<references /> | |||
Related articles: | |||
* [https://www.origsoft.com/solutions/user-acceptance-testing/what-is-an-acceptance-test-plan/ What is an acceptance test plan? - Original Software] | * [https://www.origsoft.com/solutions/user-acceptance-testing/what-is-an-acceptance-test-plan/ What is an acceptance test plan? - Original Software] | ||
* [https://docs.gitlab.com/ee/ci/pipelines.html Introduction to pipelines and jobs | GitLab] | |||
* [https://en.wikipedia.org/wiki/Functional_testing Functional testing - Wikipedia] function test ([http://terms.naer.edu.tw/detail/1279055/ 功能測試]) | |||
* 軟體測試報告 (Software Testing Report, STR) [https://www.krispmschool.com/share/sw_docs/software_test_report.php 軟體/系統測試報告(STR)文件下載-Kris專案管理學院] | |||
[[Category:Programming]] [[Category:Software]] | [[Category:Programming]] [[Category:Software]] | ||
Latest revision as of 11:43, 27 November 2018
使用者驗收測試(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專案管理學院