In my Topology, I have devices.
In (most) devices, I have multiple sessions.
Each session has a base session profile they inherit from - I've created a base session profile for each session type in my Topology (i.e. telnet, ssh, serial, cmd, webUI, etc)
Each base session profile has a single QuickCall library (Misc tab).
I have 3 very similar testcases - one uses ssh, the 2nd one uses telnet, then does a ssh from within the telnet session (i.e. It's just a telnet session from iTest's view), and the 3rd goes through a Serial Terminal Server (via telnet) to use the same calls via serial (i.e. it's just a telnet session from iTest's view):
- TestCase 1: iTest ssh to device B --> "serial" QuickCalls to run on device B
- TestCase 2: iTest telnet to device A --> ssh to device B --> "serial" QuickCalls to run on device B
- TestCase 3: iTest telnet to device C --> serial (Terminal Server "C") to device B --> "serial" QuickCalls to run on device B
In another 2 very similar testcases, one uses the Command Prompt (local commands), the other uses telnet to connect to the same device to send Command Prompt commands to:
- Test Case 1: iTest Command Prompt on itselt (PC #1) --> "cmd" QuickCalls to run on local PC #1 (Command Prompt)
- Test Case 2: iTest telnet to PC #1 --> "cmd" QuickCalls to run on telnet session on PC #1 (Command Prompt via telnet)
In both cases, I need access to the same QuickCalls - how do I setup iTest do do that so that all Session Profiles (one for ssh and one for telnet; or one for Command Prompt and one for telnet) can have a superset of a common QuickCall library? (Inheritance of QuickCall libraries - i.e. In the 1st example, the ssh session profile and telnet session profile each have their own QuickCall library, which both inherits from the same separate "serial" QuickCall library; and in the 2nd example, the QuickCall same library is inherited for the QuickCall library associated with the telnet and Command Prompt base session profiles)
More specifically, in the 1st example:
TestCase 1's initial ssh session needs access to: ssh_QuickCalls.fftc, which includes/inherits serial_QuickCalls.fftc
TestCase 2's initial telnet session needs access to: telnet_QuickCalls.fftc, which includes/inherits ssh_QuickCalls.ffts, which also includes/inherits serial_QuickCalls.fftc
TestCase 3's initial telnet session needs access to: telnet_QuickCalls.fftc, which includes/inherits serial_QuickCalls.fftc
In the 2nd example:
Test Case 1's initial command prompt session needs access to: cmd_QuickCalls.fftc.
Test Case 2's initial telnet session needs access to: telnet_QuickCalls.fftc, which includes/inherits cmd_QuickCalls.fftc.
Thanks for any help!
