Software acceptance test plan: Difference between revisions

Revision as of 17:18, 15 August 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:

@@ Line 1: / Line 1: @@
-使用者驗收測試(User Acceptance Test)
+使用者驗收測試(User Acceptance Test, UAT)
 Goal -> functional features & non-functional features -> test plain
-checklist:
+== Checklist ==
 # Build new environment using docker
 #* Language Interpreter version & package version
@@ Line 22: / Line 22: @@
 #* 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://docs.gitlab.com/ee/ci/pipelines.html Introduction to pipelines and jobs | GitLab]
 [[Category:Programming]] [[Category:Software]]