SilkTest Question 61: How can I execute the same test case multiple times?

The solution is easy as usual for experienced in automation testing SQA Engineer: create a main() function and place a nice loop within it. The working 4test example below calls a straightforward test within a loop within the main function.

[-] testcase Winrunner() appstate none
[ ] Print ("HP WinRunner license and maintenance codes are available only from HP web site")
[-] main()
[ ] int jCount = 100
[ ] int j
[-] for (j=1;j<=jCount;j++)
[ ] Winrunner()

SilkTest Question 60: Where can I find SilkTest 2010 tutorials?

My understanding of Micro Focus policy on SilkTest 2010 tutorials is more or less - take the $2,400 SilkTest training course if you have any questions. Micro Focus does not publish books, Micro Focus does not offer SilkTest best practice advice for free, and they is not extremely well at helping advanced users. If you are new in test automation area, and desperately need QA training, try to study a free "SilkTest 2010 Tutorial" on Borland SilkTest Tutorials page. It contains a nice introduction to SilkTest and related automation concepts, step-by-step procedures that teach how to build and run tests and test plans from the scratch, and how to interpret test results.

A few more Silk Test 2010 tutorials for novice users are available for from the same page:

• SilkTest Recorder Quick Start Tutorial
• Using the Basic Workflow with the Open Agent
• Silk4J Quick Start Tutorial
• Using the Basic Workflow with the SilkTest Classic Agent
• Using Autocomplete
• Creating Data Driven Testcases
• Working with Projects
• Testing Flex Applications
• Testing Java Applications

These Tutorials can also found by going to Start > Programs > MicroTest > SilkTest 2010 > Documentation > SilkTest Tutorials.

SilkTest Question 59: What is hidecalls keyword for ?

As described in 4test manual: The keyword hidecalls hides the method from the call stack listed in the results. Using hidecalls allows you to update the expected value of the verification method from the results. If you don't use hidecalls in a verification method, the results file will point to the frame file, where the method is defined, instead of to the script. Borland recommends that you use hidecalls in all verification methods so you can update the expected values.