Automated Test Frame RRAFS
---- SafTware Automation Framework Support
Author: pcl
Email: PCL2004_19@hotmail.com
Introduction:
The automated framework RRAFS is developed by Carl Negle as SAS, implemented on the IBM Rational Robot platform. About this automation framework You can go to http://safsdev.sourceforge.net/, where there is a detailed information.
purpose:
Some people define software automation tests into three development phases:
The first stage: Basic GUI test, use the model / playback tool to develop automated test scripts, this method is limited to user operations on the GUI level, editing the test script, and the edited test script, script It is unstructured, not archived, not maintainable.
The second stage: The script writer has developed to "establish a good structure, archived, robust, maintenance test", test projects become engineering projects, test scripts include errors and recovery logic, key Is the test script component can be reused
The third phase: This stage is characterized by controlling test resources, and testing design and testing automation at this level.
We have always expected the highest level of test automation, and we can really implement test automation one day. However, the content and information on automation testing on automation tests are very small, I hope to play the role of the jade from the things I wrote. Everyone studys, and improves the software test level as soon as possible.
Install RRAFS:
There are four steps to install RRAFS:
Set Playback Option
2. Decompose the RraftBasic file path to the Robotbasic file path (default path: installation path / russional / russional test / sqabas32)
3. Run setup.vbs
4. Established additional DataPool folders in the project file
Remarks:
The above operation is to assume that you have already changed the test frame, and if you don't get it can be downloaded on http://sourceforge.net/project/showfiles.php?group_id=56751, RRAFS latest version.
Detailed installation:
Set Playback Option
Set as shown:
Need to be set as above:
ON Script Command Failure: Continue Execution
ON Verification Point Failure: Continue Execution
Recommended settings:
DELAY BETWEEN COMMANDS (MilliseConds): 0
DELAY BETWEEN Keystrokes (MilliseConds): 0
Diagnostics - Timeout Delay Multiplier: 1
