Talk about non-standard automated test development tools
* 来源: * 作者: admin * 发表时间: 2019/04/16 14:15:37 * 浏览: 39
1.interface automation test tool
We often use commercial or open source tools when we start, such as QTP, RFT, etc. These are all automated tests at the interface level. Interface automation tests have certain development difficulties, but there are quite a few open source libraries. Provided, you can develop based on the above library, or some open source tools are very mature, what you do is to make changes based on the above.
For example: the tools for testing the java interface are open source tools such as aboot, swbot, and mathron. The test web interface includes selenium, watin, etc., and the mobile terminal has robotium, monkey, and the like. To be able to develop these tools twice, it is necessary to understand the principle of grabbing objects and playback, and then the processing of some configuration files. The object library is mainly XML processing. I think the general recording function can be ignored.
2. white box test tool
Some code-level testing tools, such as analysis of code coverage, analysis of code quality, etc., are relatively shallow and are not casual.
3. interface automation test tool
When developing an interface automation test tool, you first need to clarify the type of the business interface, and then master the application mode of the interface tool. The general interface tool will parse some interface definition file, and then display the interface file as an interface. You can operate the interface interface: fill in the parameters of an interface, then send it to the server, view the response, or directly return the value of the get interface. For example, the SoapUI tool is a test for the WebService system, mainly to parse the WSDL interface definition file.
Jmeter and LR can also be used as interface testing tools, such as: java interface and HTTP interface. Previously, the interface tools developed included: SNMP interface and corba interface tool, the principle is also to parse the mib and IOR interface definition files, and then set and get operations on the interface.
In the end: To develop such tools, it is necessary to clarify what is the software interface, then what the interface description file is, and finally how to operate the interface, log and result display, etc., and some are additional functions. For example, recording, recording the operation of the interface by the tester, becoming a workflow, and the like.
4. performance automation test tools
Seeing performance testing tools, it is easy to think of LR, Jmeter and the like. I use less of this tool, but I will develop some such tools based on tests of some special performance scenarios of my company's internal products.
For example, develop a tool to send SNMP network packets, simulate the maximum receiving and concurrent performance of alarms, develop a network element simulator, and simulate a large number of network elements with different IPs. You can test the largest network managed at the same time on the company's NE manager. Yuan et al.
Finally, the performance test should first be combined with the business scenario, and then master a certain performance basis and indicators, analyze the relevant interface protocols and the business that needs to be simulated, and then quickly develop the corresponding tools.
5. system application level automated test tools
This kind of tool needs to clarify the application scenario, that is, to define the requirements. For example, I have previously developed some internal department tool collections, which are specially provided for testers to perform script recording (), company-level collection and inspection tools. (External support), the benefits of this part of the tool are great. Therefore, we must not limit automated testing to testing. In fact, the efficiency of testing and development personnel, as well as the quality assurance of the company's products, can bring direct benefits to the company. Maybe a few lines of code is also a good tool to improve efficiency.
We often use commercial or open source tools when we start, such as QTP, RFT, etc. These are all automated tests at the interface level. Interface automation tests have certain development difficulties, but there are quite a few open source libraries. Provided, you can develop based on the above library, or some open source tools are very mature, what you do is to make changes based on the above.
For example: the tools for testing the java interface are open source tools such as aboot, swbot, and mathron. The test web interface includes selenium, watin, etc., and the mobile terminal has robotium, monkey, and the like. To be able to develop these tools twice, it is necessary to understand the principle of grabbing objects and playback, and then the processing of some configuration files. The object library is mainly XML processing. I think the general recording function can be ignored.
2. white box test tool
Some code-level testing tools, such as analysis of code coverage, analysis of code quality, etc., are relatively shallow and are not casual.
3. interface automation test tool
When developing an interface automation test tool, you first need to clarify the type of the business interface, and then master the application mode of the interface tool. The general interface tool will parse some interface definition file, and then display the interface file as an interface. You can operate the interface interface: fill in the parameters of an interface, then send it to the server, view the response, or directly return the value of the get interface. For example, the SoapUI tool is a test for the WebService system, mainly to parse the WSDL interface definition file.
Jmeter and LR can also be used as interface testing tools, such as: java interface and HTTP interface. Previously, the interface tools developed included: SNMP interface and corba interface tool, the principle is also to parse the mib and IOR interface definition files, and then set and get operations on the interface.
In the end: To develop such tools, it is necessary to clarify what is the software interface, then what the interface description file is, and finally how to operate the interface, log and result display, etc., and some are additional functions. For example, recording, recording the operation of the interface by the tester, becoming a workflow, and the like.
4. performance automation test tools
Seeing performance testing tools, it is easy to think of LR, Jmeter and the like. I use less of this tool, but I will develop some such tools based on tests of some special performance scenarios of my company's internal products.
For example, develop a tool to send SNMP network packets, simulate the maximum receiving and concurrent performance of alarms, develop a network element simulator, and simulate a large number of network elements with different IPs. You can test the largest network managed at the same time on the company's NE manager. Yuan et al.
Finally, the performance test should first be combined with the business scenario, and then master a certain performance basis and indicators, analyze the relevant interface protocols and the business that needs to be simulated, and then quickly develop the corresponding tools.
5. system application level automated test tools
This kind of tool needs to clarify the application scenario, that is, to define the requirements. For example, I have previously developed some internal department tool collections, which are specially provided for testers to perform script recording (), company-level collection and inspection tools. (External support), the benefits of this part of the tool are great. Therefore, we must not limit automated testing to testing. In fact, the efficiency of testing and development personnel, as well as the quality assurance of the company's products, can bring direct benefits to the company. Maybe a few lines of code is also a good tool to improve efficiency.
关闭返回