It's all about the answers!

Ask a question

RFT scripts running on different machine through RQM


Ricky Jay (281126) | asked Jul 21 '16, 5:19 a.m.
Hello,

We have 10 machines on which RFT is installed and folks are working on those. Lets say Machine Z gets corrupted or unavailable. How could we manage to run the test scripts that was recorded on machine Z to any other available machine.

I usually use the option "Use test resources that are local to a test machine" to import scripts,
1- Is this work in the above case?
2- Does RQM store the test scripts in its own repository and when running the script through RQM it would copy the script and run on any other machine ?
3- Shared repository is the way to achieve the above scenario?
4- If yes, how can we manage the test scripts on shared repository from Multiple RFT machines.

Please suggest.

2 answers



permanent link
Ara Masrof (3.2k15) | answered Jul 21 '16, 3:57 p.m.
JAZZ DEVELOPER

If you have used the option "Use test resources that are local to a test machine" when importing and have multiple RFT systems in your environment; the path you used to import from must be valid on all the RFT systems you want to execute on. For example, if you imported an RFT script named 'MyScript' using the Path “C:\RFT\”; the script must be in that file path for all the RFT systems you want to run it on

RQM does not copy the script; it creates a meta-data artifact containing the information about the script. When executing from RQM, the path of the script is referenced and run on the specified machine

In general, if you have a multiple RFT systems, using a shared repository would be the option of choice; your RFT scripts would reside in one central location. When execution the script, you can chose the system you want them run on (or set a 'favorite' system); they will be copied over at run time and executed


Comments
Ricky Jay commented Jul 22 '16, 10:49 a.m.

Thank you Ara, I understand that it cannot be achieved by using the option "Use test resources that are local to a test machine".


Coming to your point using a shared repository is the option in our case. Can you be more specific about it?

How could we create and manage a shared location/repository? what steps are needed to make sure that all the RFT scripts are on shared repository. 


Ricky Jay commented Jul 25 '16, 8:37 a.m.

 @ara, Can you please help?


permanent link
Ara Masrof (3.2k15) | answered Jul 25 '16, 9:01 a.m.
JAZZ DEVELOPER
Here are the contents of the Help topic Making shared test resources available

Before you can use test resources from a shared network location, an administrator must make the resources available.
Before you begin
For Rational® Quality Manager running on Windows servers, Rational Quality Manager must be able to access the shared resource using the UNC naming convention. For example, if the test resources are stored on a server in the C:\MyRemoteAssets directory, an administrator must map a UNC path, such as \\9.27.150.168\RemoteTestAssets or \\OurTestServer\RemoteTestAssets to those test resources.

For Linux, AIX®, and Solaris servers, Rational Quality Manager must be able to access the shared resource using an appropriate pathname. The shared resource locations can be pre-mounted or can be configured to auto-mount when used. For example, to access shared resources from a Windows file server when your Rational Quality Manager server is running on Linux, you must mount the Windows share on Linux. The following is an example command for a RHEL 6 machine:

mount -t cifs //machinename/mymachine -o username=userid,password=XXXXXX /mnt/WinShare

If you need to use a domain ID and password, you must specify the username in the form id@domain. Also, the mount command usually requires root (super-user) access. After you run the mount command, you can access the files in the Windows share from the directory that you specified (for example, /mnt/WinShare).

The user must be able to access the shared resources without having to supply a password.

About this task
To make shared test resources available to Rational Quality Manager:
Procedure
Log in as a user who has permission to save and modify a project area. This can be any one of the following:
A user granted permission to save and modify a project area in the process configuration.
A user who is an administrator of the project area.
A user who is granted either the JazzProjectAdmins or JazzAdmins repository group permissions.
Click the Admin (Administration) icon in the upper right portion of the banner and select Manage Project Properties.
Click Shared Resource Locations.
Click the Add Resource Location icon (Add).
Type the path to the shared location, using the UNC naming convention on Windows or the full path name on Linux, AIX, and Solaris.
Click Save.
Results
After the shared resource has been made available, users can create test scripts that reference that resource from the shared location.

You would then need to copy your RFT scripts to that shared repository

From some additional searching I found this article that may be helpful (its a few years old but the concepts are still valid )
https://rationaltester.wordpress.com/2009/03/13/integrating-rational-functional-tester-and-rational-quality-manager/

Comments
Ricky Jay commented Jul 25 '16, 9:55 a.m.

I see..

you mean to say we need to copy scripts to the shared repository every time we create a new RFT scripts? We have many test machines and this would cause issues to keep copying and update the shared repository.

Is there any way to get the scripts location updated automatically? Could SCM be utilized to serve our purpose?


Ara Masrof commented Jul 25 '16, 12:43 p.m.
JAZZ DEVELOPER

I don’t believe RFT supports a single project on a network drive that multiple instances of RFT can connect to, but you probably want to check with RFT support

If so, you could us that as the basis of your Shared Resource Repository for RQM; if not, you would need to manually copy them over or set up some sort of a batch file that does it automatically

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.