some newbie questions
I have just started to evaluate SilkTest (but evaluated some other tools before (Robot, QTP, WinRunner) so that I can compare SilkTest a little bit to the other ones).
Now I have some basic questions:
1.) Maybe I'm really too stupid but I couldn't find a User Guide up to now. So can anybody help me out please!
2.) Is there a possibility that the script doesn't terminate if a Verification fails??
3.) If you debug your script and a Verification fails (and so the script terminates), how can you update the expected values in debug mode?
4.) If a Bitmap Verification fails I can see the difference in the Bitmap Comparison Tool. If I want to update the expected bitmap: Do I have to overwrite the expected bitmap file with the result file or is there another way to do this?
5.) I think there is no tool where you can see a list of your verifications and edit them, is there? So if I want to change e.g. the properties that should be verified, do I have to do this manually/ programmatically in the script?
6.) About Data Driven Tests: I created a .xls table with just one column where I filled in several values (strings) and then I create a data driven testcase. Now I want to run the test on all rows but not the whole script should be run several times but just a certain piece of the script. So how to do this?
7.) Last question: Has anyone of you ever tried to record/playback on Windows' Computer Management? It didn't work for me...
Hope you can help me and maybe you have some tips how to ease the getting-started-process with SilkTest! The other tools I evaluated were MUCH easier to use and understand and all the things I asked above worked with the other tools so I think they should work with SilkTest, too...
Re: some newbie questions
1.) All guides are assumed by the online help
2.) Try exception handling by using 'do...except'
3.) with do...except, the script won't terminate,
with 'view|excpression' in debug mode you can
4.) You can capture bitmap by using the bitmap tool,
shipped and installed with silktest.
5.) look in online help by searching for 'property sets'
6.) I never worked with data driven tests, sorry.
We use csv-testdata and wrote our own framework with
4Test, the so called scripting langauage of silktest. The (rudimental) object oriented philosophy and the posibility to use external dll-files
and databases and excel worksheets respectively
makes SilkTest very flexible, but I know how
you feel now. But with this forum, we could
sail round each problem we ever had ;o)