Error "Unable to create procedure" if recorded steps invoke multiple sessions

Question

question

amichaels asked Jun 10, '10 Spirent_Admin edited Mar 18, '13

Error "Unable to create procedure" if recorded steps invoke multiple sessions

![alt text][1]

I'm using quick calls to interface with a tcl api for a DUT. Some of the quick calls use a command prompt session to manage temporary files.

After I stop capturing, iTest takes me through the new test case wizard. When I click "Finish", I get the above error. Is my only option to copy/paste the steps from the capture view? Or is there some other way to avoid this error? Each of the quickCalls that invoke the command prompt have an open step, so I'm not sure what the error means when it says that I must include an open step for each session.

[1]: /storage/attachments/1248-itest%20error.jpg

iTest error message quickcall (qc)

itest error.jpg (36.2 KiB)

10 |950

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

Answer 1 · 2010-06-10T22:46:13Z

PatrickH answered Jun 10, '10 PatrickH posted Jun 10, '10

In such scenarios, it is important to open each session after having started capture. If you have a session already open when you start capture, then the wizard is unable to add the open step for the session that was already active.

If you are sure that the quick calls that you're invoking are opening the sessions for you, then I agree that there seems to be a problem here. In that case we would have to investigate this scenario and see if a fix is required or something else is going on.

1

10 |950

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

amichaels ♦ commented · Jun 10, 2010 at 10:54 PM

my workflow is:

- start capture

- start a new session from my session profile

- once the session loads, execute several quickcalls in sequence. 2 of these start command prompt sessions.

- when I'm done with my quickcalls, I close the session

- finish capture

- go through test case wizard, get error

I've attached the project

0 ·

my_project.itar (15.7 KiB)

Answer 2 · 2010-06-10T22:54:08Z

sreekanthreddy answered Jun 10, '10 sreekanthreddy posted Jun 10, '10

To over come this error we need to set a open step for each session.

10

10 |950

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

AdamB commented · Jun 10, 2010 at 10:56 PM

sreekanthreddy wrote:

To over come this error we need to set a open step for each session.

Yes. You could then delete the sessions from the test case after.

Alternatively, if you open the "Capture View" you could drag in steps from each session, a session at a time, into the test case.

0 ·

amichaels ♦ AdamB commented · Jun 10, 2010 at 10:59 PM

Thanks, AdamB. I'm trying to show this in a demo, so I'd like it to be smoother. I feel copy/paste from the capture view will distract from the point I'm trying to make with quickcalls. I'm looking for any other alternatives.

-Andy

0 ·

amichaels ♦ commented · Jun 10, 2010 at 11:01 PM

Sreekanth, Maybe I'm missing something, but I'm not sure what it means to "set an open step" for a session. The procs I've defined include open steps for the command prompt session type. Is that what you mean, or something else?

-Andy

0 ·

koelze amichaels ♦ commented · Jun 10, 2010 at 11:33 PM

Hey Andy,

I'm really sorry you're having trouble with this. I took a look at the files inside the iTar, and it looksl ike all of this =should= work. In fact, I opened up the session profile (getting rid of the initialization script, because I didn't have the required Tcl libraries), and I just ran some of the quick calls before rendering it into a test case; it all seemed to work fine for me. Can you do me a favor? Can you go to the capture view and save the relevant portions as a capture report? Also, can you take a screenshot of the entire iTest window (including the capture view) right after you click the "Add to Test Case"? This'll give us an idea what was selected and what it's actually trying to render.

Thanks,

Kevin

0 ·

amichaels ♦ koelze commented · Jun 10, 2010 at 11:40 PM

Kevin, I've attached the capture report. Oddly enough, when I "add to test case" from the capture view, I don't get the error. I only get the error from a newly finished capture.

298iBE3EDB040BF39FFB

0 ·

cr.2010-06-10.18-36-38.ffcz (12.3 KiB)

itest window after add to test case.JPG (283.9 KiB)

koelze amichaels ♦ commented · Jun 11, 2010 at 12:07 AM

Okay, I can reproduce this now. I'm filing a bug for this; would using the "Add to test case" for the individual session work for your demo? I always end up using it, because I never remember to actually press start capture before I start sessions.

For what it's worth, this only affects the workflow where you click Start Capture, then run quick calls that open other sessions, then Finish capture. Any other workflow this should be fine.

0 ·

amichaels ♦ koelze commented · Jun 11, 2010 at 03:57 PM

KevinO wrote:

Okay, I can reproduce this now. I'm filing a bug for this; would using the "Add to test case" for the individual session work for your demo? I always end up using it, because I never remember to actually press start capture before I start sessions.

For what it's worth, this only affects the workflow where you click Start Capture, then run quick calls that open other sessions, then Finish capture. Any other workflow this should be fine.

Yes, I can use add to test case for the demo. Your last statement is correct. Thanks!

-Andy

0 ·

AdamB amichaels ♦ commented · Jun 11, 2010 at 12:12 AM

Right now with iTest, capture only has three modes that work and can be rendered into a test case:

1. one session with an open step for that session

2. multiple sessions that all have open steps

3. one session that has no open step, but the test case HAS a session of that type in it

What won't work is trying to add steps from multiple sessions where one or more of those sessions does not have an open step.

This was tried, but there were lots of confusion when trying to associate various sessions with other sessions. It works for the super simple cases, but was problematic for more complex situations. That being said, we are working to find a cleaner way to handle those situations.

Are you doing your capturing and adding from w/i the new ActivityUI in 4.0 or just doing this through the Capture View in 3.4?

0 ·

amichaels ♦ AdamB commented · Jun 11, 2010 at 04:02 PM

AdamB wrote:

Right now with iTest, capture only has three modes that work and can be rendered into a test case:

1. one session with an open step for that session

2. multiple sessions that all have open steps

3. one session that has no open step, but the test case HAS a session of that type in it

What won't work is trying to add steps from multiple sessions where one or more of those sessions does not have an open step.

This was tried, but there were lots of confusion when trying to associate various sessions with other sessions. It works for the super simple cases, but was problematic for more complex situations. That being said, we are working to find a cleaner way to handle those situations.

Are you doing your capturing and adding from w/i the new ActivityUI in 4.0 or just doing this through the Capture View in 3.4?

OK. So, the situation where I call a procedure, and that procedure opens a session, violates the above 3 conditions? I suspect this is the root of the error I'm seeing.

I'm using 4.0, but I do capture the same way I did in 3.4: clicking "Start capture" in the Test case development perspective, starting my session, then clicking "finish capture".

-Andy

0 ·

koelze amichaels ♦ commented · Jun 11, 2010 at 04:53 PM

If a QuickCall were to open a new session and leave it open, then the user manually interacts with it (or manually has to close it), then, yes, it would violate that; however, your model is completely fine. Opening new sessions inside a QuickCall, doing some things, and closing the session right away (which your library does) should work; it's a bug that it doesn't work with the start/finish capture workflow,.

0 ·

question