posted 03-19-2002 07:14 AM         

quote:

---

Originally posted by pcl9097:
So my "Navigation Script/Core Data Driven Engine" is actually written in TSL (if I was using WinRunner)? Similar to how yours (Atlee) is written in SilkTest?

So if we had to test this on an App running on Unix, I would have to also create a "Navigation Script/Core Data Driven Engine" for XRunner?

Thanks.

---

In my case, yes, that is correct. Everything except the test input tables are written in the automated tools' scripting language. My input tables are either Excel or Access, and that is the only other utility we use. I don't know if this is the best way to do it, but it was the only way that made sense for our testing.

I think that you would need two test harnesses if you run on a PC and under Unix using Mercury. There shouldn't be a big difference in the scripts, but there will definitely be differences. I haven't used the two products at the same time, so I don't have a lot of insight into what is different. It may be possible to use some of the same scripts - if you are interested I'm sure some of the folks who participate in the WinRunner forum would be happy to help. I think you will definitely need two sets of window declaration files at a minimum.

While I haven't used the Unix feature of SilkTest, it does support running on both a PC and Unix using the same scripts and window definitions. It may be worth looking into if you need to support both. That is one of the reasons we went with Silk in the first place. It may be cheaper in the long run to purchase a new tool that is better suited to your application. Just a thought ....