Software acceptance test plan: Difference between revisions

Revision as of 14:40, 6 April 2018

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

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

checklist:

Build new environment (version & package version were defined) using docker
Deploy and run the codes
Testing
- Testing by small amount data, large amount data
- Expected or un-expected result
- Validate the data flow: (1) format of input data & output data e.g. data type of column, (2) rows count of data or file size^[1]
  - 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

References

@@ Line 4: / Line 4: @@
-Execution environment:
+checklist:
-* (1) build new environment (version & package version were defined) using docker
+# Build new environment (version & package version were defined) using docker
-* (2) deploy the codes
+# Deploy and run the codes
-* (3) 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 data flow: (1) format of input data & output data e.g. data type of column, (2) rows count of data or file size<ref>[https://stackoverflow.com/questions/5920333/how-to-check-size-of-a-file bash - How to check size of a file? - Stack Overflow]</ref>
+#* Validate the data flow: (1) format of input data & output data e.g. data type of column, (2) rows count of data or file size<ref>[https://stackoverflow.com/questions/5920333/how-to-check-size-of-a-file bash - How to check size of a file? - Stack Overflow]</ref>
-*** If the input data came from previous step, you should check the format of data generated by previous step before executing the process.
+#** 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
 References