I'm seeing some unexpected behavior using quickcalls I defined for the vSphere session.
The original code was a procedure library that called the built-in actions for the vSphere session type. I converted this code to quickcalls so that I could add some custom actions of my own.
It seemed to work until I ran the code in our headless Jenkins environment. We use itestcli to execute our tests on CentOS 5.10. The user running itestcli has no shell, and no display.
When I run my test using the quickcalls, I get an "internal error : workbench not ready". I do not get this error when running the tests using the procedure library version of the code. The odd part is that it is not my quickcalls that throw the error, it's the built-in action that raises the error. Specifically, the call to "PowerOffVM" is where I get the error. I'd have expected this to happen on the "open" step, or even my own quickcalls (which are called before PowerOffVM).
Does anyone have any insight on this?
Is it possible to upgrade the flash version for the built-in web browser on CentOS 5.10? 2 Answers
iTest 5.1 Linux 64-bit crashes when I commit to SVN 1 Answer
arguments don't show when calling quickcall 0 Answers
Error "Failed to create Tcl interpreter: Cannot run program [path]/tclsh8.5" 0 Answers
iTest can't find a test case file 4 Answers
Copyright 2008- Spirent Communications, all rights reserved. Terms and Conditions.