Software acceptance test plan: Difference between revisions

Latest revision as of 11:43, 27 November 2018

使用者驗收測試(User Acceptance Test, UAT)

Goal -> functional features & non-functional features -> test plain

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.
Progressive update
- Incremental updates: How to apply new data to the current model
- How to use new data to update the model

References:

Related articles:

@@ Line 30: / Line 30: @@
 * [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/ 功能測試])
-* [https://www.krispmschool.com/share/sw_docs/software_test_report.php 軟體/系統測試報告(STR)文件下載-Kris專案管理學院]
+* 軟體測試報告 (Software Testing Report, STR) [https://www.krispmschool.com/share/sw_docs/software_test_report.php 軟體/系統測試報告(STR)文件下載-Kris專案管理學院]
 [[Category:Programming]] [[Category:Software]]