question

takabanana avatar image
takabanana asked amichaels answered

Questions on QuickCall <--> Session Profile link

1. I realize that QuickCalls have to be tied to a Session Proflie - unfortunately, this makes a series of commands that work equally under Telnet/SSH/Serial to be wastefully duplicated into their own QuickCall libraries.  Is there a better way to do this without having to duplicate and maintain separate QuickCall files/code?  Is there any way i can use multiple Sessions to use a single QuickCall file (i.e. Telnet/SSH/Serial)? 

 

2. On a related note, am I correct to say that to make a QuickCall, the following to HAVE to link/point to each other?  This makes a similar multi-to-one limiting issue for #1 above, although this is multiple QuickCalls files to a single Session... I can't use multiple QuickCall files for any one single (base) Session?? 

 

In Session Profile (.ffsp) --> Misc tab --> QuickCall 

  • 2011-11-21_111142.png

In QuickCall (.fftc) --> General tab --> QuickCall

  • 2011-11-21_111216.png

 

 

 

iTestquickcall (qc)
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

msandeep avatar image
msandeep answered msandeep posted

Hi,

 

1# Unfortunately, in iTest we cannot use multiple QuickCall libraries with single session profile and multiple session profiles for single QuickCall library.We have to create seperate QuickCalls for each session profile.

 

2# Yes, your understanding is correct. Whatever the QuickCall path we have given in Session Profile (.ffsp) --> Misc tab --> QuickCall that QuickCall should contain the same session profile path under QuickCall (.fftc) --> General tab --> QuickCall.

 

Thanks,


 

 

 

6 comments
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

takabanana avatar image takabanana commented ·

OK - so unfortunately, if I have a bunch of command-line commands to a device that has serial/telnet/ssh capabilities, I have to duplicate and maintain the QuickCalls across separate files, which tie to each of the (serial/telnet/ssh) session profiles of the device?

 

Thanks.

 

0 Likes 0 ·
msandeep avatar image msandeep takabanana commented ·

Yes, your understanding is correct. You have to create seperate/duplicate the Quickcall linraries with respect to the session profiles (telnet/serial..) you are using.

 

Thanks,

0 Likes 0 ·
kamesh avatar image kamesh msandeep commented ·

I have the same issue!

 

Can this be taken as a feature request? it is waste of time and head ache in maintaining these copies.

 

BTW Is it possible to create a symbolic link for the quick call with different file names for each session profile? (dont know how it would work in windows and SVN, if this can be done just for fanfare atleast it will be wordaround)

 

Thanks

 

0 Likes 0 ·
msandeep avatar image msandeep kamesh commented ·

Hi Kamesh,

 

Could you please elaborate your suggestion to make us understand more

 

BTW Is it possible to create a symbolic link for the quick call with different file names for each session profile? (dont know how it would work in windows and SVN, if this can be done just for fanfare atleast it will be wordaround)

 Thank You!

0 Likes 0 ·
kamesh avatar image kamesh msandeep commented ·

This is what are are planning to do as a work around. Let me know if this will work

 

Create quick call file for the sessions

 

telnet.fftc

ssh.fftc

console.fftc

 

Create a lib called cli.fftc, this lib will have all procedures that we want to execute. The individual quick call will have wrapper procedures which will call the proc from cli.fftc

This way i have to write the logic in one place rather than repeating it for each sessions

 

 

0 Likes 0 ·
msandeep avatar image msandeep kamesh commented ·

Hi Kamesh,

 

Instead of a quick call, you could go for procedure library

 

you could create a sample lib having one or more session related.

 

From each test case call the desired procedure (of the procedure lib) and pass the session value so it can ivoke the desired commnds with the assocaition of the session value.

Please refer the below screen shots:

Proc lib:

proc_lib.png

 

Test case:

testcase.png

 

Please be posted how it goes! Thank you!

0 Likes 0 ·
proc_lib.png (59.0 KiB)
testcase.png (33.4 KiB)
amichaels avatar image
amichaels answered

I realize this is an old post, but for future searchers, this isn't as big a limitation as it may sound. If you have multiple devices that have the same commands, you should create a generic base session profile and create your quickcalls for that base session profile. Then, all devices that inherit from the base session profile have access to the quickcalls defined for base. Furthermore, a child session profile can define an additional quickcall library. In this new library, you can override any inherited quickcalls, or leave them alone. TL:DR: use inheritance.

10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.