FanfareSVT to iTest Migration

[deepti]

Can i get more help on --exportPath and --exportProject needed for creating itar? are there any library dependencies for these commands?

Thanks

[KumarS]

One can create itars in two ways:

1. Using iTest GUI - File->Export->iTest> Export projects as iTars

2. Using iTestCli.

This is the syntax for using itestcli:

itestcli.bat -w <full path to your workspace folder> --exportPath <path to directory where itars will be exported>

This will export all projects in the workspace.

If you only want certain projects, you can use --exportProject a,b,c  where a, b and c are just the names of the projects (not the paths).

[deepti]

Hi,

i tried using the itestcli command to generate itars, but I am facing the following problems :

i use cvs for source control, so before creating a new itar, i fetch the latest copy of itest project from cvs into /usr/local/temp as xxx.

and then is do

./itestcli -w /usr/local/temp/ --exportProject xxx  --exportPath /home/qatest

But i get the following error

Unable to connect to iTest workspace server.

i tried to use

./itestcli -w /usr/local/temp/xxx --exportProject xxx  --exportPath /home/qatest

but still i get

No project to be exported

Is something wrong with the way i am using the path to the workspace?

Thanks

[KumarS]

Can you run the same earlier command with "-d" option? This will give you more information about the error.

I would recommend that you check the following:

1. Make sure that you get all your cvs stuff under a folder under /usr/local/temp. Do not get all the stuff under temp directly.

2. Make sure that you use this folder as your workspace. If the folder was "foo", you would use: -w /usr/local/temp/foo

The reason for this is that your temp folder can have huge number of files and some very special device files which can get iTest process stuck on trying to detect how many projects are there in temp folder. You are much safer creating a folder under temp and getting all the projects under there and using that folder as your workspace.

[deepti]

I followed your instructions, now my directory /usr/local/temp1 has only  Vyatta as the itest folder.

but i get following error

Directory:/usr/local/temp1/Vyatta
Workspace directory exists
Connecting to iTest workspace
Attempt: 0
iTest workspace server is NOT running
serverprocess file NOT FOUND in workspace
serverprocess file NOT FOUND in workspace
serverprocess file NOT FOUND in workspace
serverprocess file NOT FOUND in workspace
serverprocess file NOT FOUND in workspace
serverprocess file NOT FOUND in workspace

[KumarS]

Something weird is going on. I suspect that iTest process is getting launched with a workspace folder which has a giant subtree of folders underneath it. Anyway - I think you will need to contact Fanfare support to help with this. I still suspect that it is some kind of set up error.

[deepti]

well now the error is somewhat different

Verifying workspace location: /usr/local/temp/itest-vyatta
Directory:/usr/local/temp/itest-vyatta
Workspace directory exists
Connecting to iTest workspace
Attempt: 0
iTest workspace server is NOT running
Starting workspace server...
Starting itest with arguments:
/opt/Fanfare/iTest_3.4/itestclihelper.sh
-nosplash
-data
/usr/local/temp/itest-vyatta
-configuration
@user.home/.itestcliconfig_3.4
--headless
--debug
--runtime
--idleTime
15
Proc: java.lang.UNIXProcess@f84386
Waiting for server to start
serverprocess file NOT FOUND in workspace
Debug mode is set to TRUE.
found serverprocess file in workspace
Deleting server launching flag file
Server port:40548
Connecting to server at:40548
Connected
Connection verified
No project to be exported

Seems like it is not able to get through the project.

the command im using is:

itestcli -d -w "/usr/local/temp/itest-vyatta" --exportPath "/home/qatest/itars/" --exportProject itest-vyatta

[deepti]

seems like itestcli exportProject doesnt export any project whose name is other "my_project". i created a itest project from scratch by adding 2 other folders to the project and the exportProject command fails for it.

whereas, it creates an itar for "my_project" project.

is this a bug??

[KumarS]

We have verified this functionality many times. I do not suspect this is a bug - but most likely a set up issue. Are you sure "itest-vyatta" is a project under the workspace? Check if you "itest-vyatta" folder under your workspace folder and then check if there is a .project file in that folder. Dump the contents of this file on the screen and check if it looks valid xml.

I still suggest that you contact support as we have been discussing this for a while without being able to help you get this fixed.

[deepti]

well, the support is looking into this since yesterday morning.