Automated test case selection and manual comparison of the advantages and disadvantages of automated testing
1. Precautions for the selection of automated test cases
2. Comparison of manual test cases and automated test cases
Manual test cases
1. Better exception handling ability, which can verify whether the function of the current step is correct or not through artificial logic judgment.
2. Manual execution of use cases has a certain step-jumping nature. 3. Manual test tracking step by step, able to locate the problem in detail. 4. Mainly used to find functional defects
automated test cases
1. The execution object is a script, and any judgment requires a coding definition.
2. Strong correlation between use case steps. 3. It is mainly used to ensure the correct and complete functions of the main body of the product and to free the testers from the tedious and repetitive work. 4. At present, the automated testing phase is positioned in smoke testing and regression testing.
By comparison, we can see that there is a big difference between manual test cases and automated test cases. Therefore, manual test cases cannot be directly "translated" into automated test scripts.
Through the comparison of their characteristics, it can be clearly recognized that automated testing cannot completely replace manual testing. The purpose of automated testing is only to free testers from the tedious and repetitive testing process and spend more time and energy. Dive into more valuable testing, such as exploratory testing. Automated testing is more used for smoke testing and regression testing; therefore, the author prefers semi-automated testing, where repetitive work is handed over to tools, and testers complete more valuable non-repetitive work.
Precautions for the selection of automated test cases:
1. Not all manual use cases should be converted to automated test cases.
2. Considering the cost of script development, do not choose use cases with too complicated processes. If necessary, consider splitting the process into multiple use cases to implement scripts. 3. The selected use cases can preferably be constructed into scenarios. For example, a functional module is divided into n use cases, and these n use cases use the same scenario. The advantage of this is that it is convenient to build a keyword testing model. 4. The selected use cases can be purposeful. For example, this part of the use case is the use case for smoke testing, the other part is the regression test, etc. Of course, there will be overlapping relationships. If the current use case does not meet the requirements, then the only option is to modify the use case to suit the script and requirements. 5. The selected use case can be the cumbersome part that you think is repeated execution, such as field validation, prompt message validation and so on. This part applies regression testing. 6. The selected use case can be the main process, which is suitable for smoke testing. 7. Automated tests can also be used to perform configuration checks and database checks. These may go beyond manual use cases, but are also part of use case extensions. Project leaders can be selectively added. 8. If you need to construct some complex data or repeat some simple mechanical actions during manual testing, tell the automated script and let him help you. Maybe your efficiency has improved again as a result.
Automated test case selection and manual comparison of the advantages and disadvantages of automated testing
1. Precautions for the selection of automated test cases
2. Comparison of manual test cases and automated test cases
Manual test cases
1. Better exception handling ability, which can verify whether the function of the current step is correct or not through artificial logic judgment.
2. Manual execution of use cases has a certain step-jumping nature. 3. Manual test tracking step by step, able to locate the problem in detail. 4. Mainly used to find functional defects
automated test cases
1. The execution object is a script, and any judgment requires a coding definition.
2. Strong correlation between use case steps. 3. It is mainly used to ensure the correct and complete functions of the main body of the product and to free the testers from the tedious and repetitive work. 4. At present, the automated testing phase is positioned in smoke testing and regression testing.
By comparison, we can see that there is a big difference between manual test cases and automated test cases. Therefore, manual test cases cannot be directly "translated" into automated test scripts.
Through the comparison of their characteristics, it can be clearly recognized that automated testing cannot completely replace manual testing. The purpose of automated testing is only to free testers from the tedious and repetitive testing process and spend more time and energy. Dive into more valuable testing, such as exploratory testing. Automated testing is more used for smoke testing and regression testing; therefore, the author prefers semi-automated testing, where repetitive work is handed over to tools, and testers complete more valuable non-repetitive work.
Precautions for the selection of automated test cases:
1、 不是所有的手工用例都要转为自动化测试用例。
2、 考虑到脚本开发的成本，不要选择流程太复杂的用例。如果有必要，可以考虑把流程拆分多个用例来实现脚本。
3、 选择的用例最好可以构建成场景。例如一个功能模块，分 n 个用例，这 n 个用例使用同一个场景。这样的好处在于方便构建关键字测试模型。 4、 选择的用例可以带有目的性，例如这部分用例是用例做冒烟测试，那部分是回归测试等，当然，会存在重叠的关系。如果当前用例不能满足需求，那么唯有修改用例来适应脚本和需求。 5、 选取的用例可以是你认为是重复执行，很繁琐的部分，例如字段验证，提示信息验证这类。这部分适用回归测试。 6、 选取的用例可以是主体流程，这部分适用冒烟测试。 7、 自动化测试也可以用来做配置检查，数据库检查。这些可能超越了手工用例，但是也算用例拓展的一部分。项目负责人可以有选择地增加。 8、 如果平时在手工测试时，需要构造一些复杂数据，或重复一些简单机械式动作，告诉自动化脚本，让他来帮你。或许你的效率因此又提高了。