Benefits of version control in a software project doesn't need any explanation. Adopting the same in test automation will benefit even teams have more than one member. In this post, we can see, what are all the files needed to be checked in the version control and how to maintain the setup.
Most of the files generated by QEngine can be opened using a text editor. Only files with QED extensions are binary files. You can only import those files in QEngine.
When you create a suitea folder with the same name created under
Conf folder - Has all the configuration related files
dataset - Contains data files
webscripts - Contains script files. Every script created will have a folder with the same name, which contains .wcs file and a map file if the script uses local level map. Information about the recorded objects is stored in an xml file which will be located in the conf folder, if the script uses global level map.
All the three folders can be checked in the version control system. If you're using the custom scripts files which will be located in
You can replace the files in the same directory, if the original ones are lost or if you want to revert to the previous entires.
Rajasankar
rajasankar at zohocorp dot com
Here i am going to discuss about the new recording option in QEngine which actually incorporates Recording / Playback and Manual Scripting.
In Record / Playback type of script authoring, normally the element data will be stored in a external Map file, and during playback the play engine will read the map file and fetch the required data from it and use it for identification in the DOM. In this mode, the tester will not be involving in the scripting much. But if there is any change in the GUI, then it will be difficult for the user to identify the property changed and modify the same in the map file.
In Manual Scripting, you have to author the script with some dynamic functions, where all the required element data will be stored in the script file itself. So, it will be clear to the user, which element is being handled and flow of script. In this mode the user has to author the script manually knowing all necessary data for element identification in the DOM. If there is any GUI changes, it will be easy for the tester to modify the details in the script itself.
QEngine introduced a new recording mode called Expert Mode. Using this you can record the script in manual authoring mode, thus the object repository (Map file) will not be required. Actions will be recorded with dynamic functions and all required element data will also be present in the script file itself.
This recording mode eases the tester from knowing all the element identification properties and manually authoring the scripts. The power of Manual Script Authoring can be attained in recording mode also.
While start the recording itself you can choose to record in Record in Expert Mode or while creating the new script check the check box for Record in Expert Mode.
Hope this will be helpful for you to understand and automate your scripts quickly in the Expert Mode Recording.
Regards,
Raghavan
srinivasar at zohocorp dot com
NetBeans released support Python recently. Check the features here
I've tried to use that IDE for editing QEngine custom scripts. Here are the steps,
1. Download and install the EA from here,
2. Create a new project. While creating the project, include the /QEngine home/jars folder in the Python path
3. Wait for NetBeans to scan and index the added folder
4. Now, you can use the IDE editor for editing custom script files including code completion.
Try and let me know.
Rajasankar
rajasankar at zohocorp dot com
