to sum up:
1) Features basic implementation, test cases are expanded
2) WinRunner, Quick Test debugging is not strong enough, error prompt is incorrect, and the Robot error message is simple. The wrong position is not accurate.
3) Quick Test has unstable places. The script has been developed and the process needs to be reused to run. It may have a relationship with the settings.
4) The Quick Test development environment can be transplanted into the VB development environment, and the reference objects in VB can be developed directly.
5) Automation Tests often run together, do not require users to start manually. In three test tools, you can reach a multiple script running together.
For example: WinRunner
Develop recorded scripts into functions.
1. Change setting, File-> Test Properties-> Test Type (Compiled Module).
2. Public function login_ok ()
{
Join the script
}
Robot
1. Record scripts join to lib
One. Establish a library source "demo" file, organize the test script as a function
SUB login_ok ()
Join the test script
End Sub
save
two. Establish Library Head "Demo" file
Declare Sub Login_ok Basiclib "Demo"
three. Add header file Demo in the main script
2. Call the script directly
Callscript "test"
Note: The second method is generally used when all test scripts are used for a test engineering. He cannot reach the purpose of the script share.
QuickTest
1. Add a new action directly to the script to achieve the purpose of continuous testing
TREEVIEW is right-click Add Action COPY
Stability evaluation:
Three test tools throughout the use process WinRunner, QuickTest test tool test environmental factors have a lot of problems during recording and return visit. Robot is relatively small by environmental impact.
Comprehensive comparison
1. From ease of use, stability, and scalability, WinRunner is not suitable for Web functional test. He identifies that the Web object is relatively poor. The existing scripting function cannot solve the problem of the identification of web object elements. It is necessary to develop a lot of scripts. To support him for Web testing capabilities, the workload is high, and the testers are required to be too high. The previous investment is too large, and the income is not obvious.
2. Robot relative to other tools, power is powerful. But to reach the script sharing requires a certain trick, try to avoid the addition of the authentication point in the class file (Robot comes with it), through other means. There is a difficulty for testers without programming experience.
3. QuickTest is a tool for web testing, so regardless of script readability, or the stability of script development is worthy of appreciation. But the debug environment is relatively poor.
4. Through comparison, individuals think that QUICK TEST and RATIONAL ROBOT are more suitable for web testing. However, QuickTest only supports VBScript, so that attention should be noted that VBScript does not support language features, such as declaring variables as much as possible without taking type, file operation is trying to use FileSystemObject objects.
5. Test tools can be used at all two tools.
