I finally downloaded it and looked at it as part of a MI QTP download titled something like "Expert Series."
It seems like a very simple example of a typical function-driven framework. I think it may be a good way to illustrate the alternative way of using QTP, for people who have never been exposed to this.
I not quite sure what you mean by trying to apply it. The framework I already use is essentially a similar concept, though much more sophisticated.
I noticed that the notes that came with it suggested a kind of "plain language" approach, which was not implemented in the saffron example. For example, using language from a manual testcase such as "Click on the Get Quote button" as test code. This is not something I would try to implement, but I am aware of others who have (as a pointless exercise, imho)
Well i am really not sure why make another language of coding over QTP VBScript. I know not all would agree with my thoughts, but i really dont fancy creating another way of coding in QTP and then say we make it easier to code.
I think that the aim of making testing such that someone can type a sentence like "Verify the account balance displayed is correct for the selected account" and have this actually perform the test, is a marketing pipedream. Trying to pry testing out of the hands of QA professionals into the hands of lesser-equipped lay folk.
Do people try to warp stuff like C++ coding like this? Not that I've ever seen or heard of.
There is no trial version of SAFFRON. It's just a small framework that someone has put together. It's available from the mercury support site. I can't see anything that suggests it can not be distributed (i.e attached here - although if you have a liceneced copy of QTP you should be able to access the support site anyway)
Firstly its a very basic demo with hard coded values.
I think it has some potential and I will take some of the code and use it in my project.
I always thought the generated lines of code in QTP were to long. Why do we need to know the Browser Page Window on every line of code. I have gone down the path of only needing these values when they change.