Software acceptance test plan: Difference between revisions

From LemonWiki共筆
Jump to navigation Jump to search
mNo edit summary
Line 29: Line 29:
* [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://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/ 功能測試])


[[Category:Programming]] [[Category:Software]]
[[Category:Programming]] [[Category:Software]]

Revision as of 15:00, 17 August 2018

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

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


Checklist

  1. Build new environment using docker
    • Language Interpreter version & package version
    • System requirement: e.g. CPU & memory usage
  2. Deploy and run the codes
  3. Testing
    • Testing by small amount data, large amount data
    • Expected or un-expected result
    • Validate the dataflow:
      • Format of input data & output data
      • 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.
  4. 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

References:

Related articles: