2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2007

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] Propogating procedure paremter values / forcing immediate expansion

  • Subject: Re: [QF-Test] Propogating procedure paremter values / forcing immediate expansion
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 21 Jun 2007 16:14:05 +0200

Hi Adrian,

perfect analysis. Everything you wrote is correct.

We are implementing an option to switch between defaulting to
immediate or lazy variable binding (plus the $_ and $! syntax for
individual variables) and are also contemplating further variable

This will not become official before QF-Test version 2.3 later this

So what about QF-Test 2.1 and 2.2? Version 2.1 will be released as
soon as possible as a development release with the goal to complete
SWT testing with features like image checks, snapshots and Drag&Drop
recording, plus a handful of non-SWT features. Version 2.1 will lead
to the stable medium upgrade 2.2.

At some point - possibly even before 2.2 is ready - development
version 2.3 will be released. This is the development version for the
next major release 3.0 with support for Web testing. The variable
changes are a major paradigm change for QF-Test, so a major release is
a good "home" for these.

Plans change, of course. I'm just trying to give people an idea about
the way things are looking right now to prevent the usual "when will
... be ready?" questions :-)

To come back to your original question: You'll need to use the
setVariable workaround for now.

Best regards,

"Adrian Chamberlain (BE/ETL)" <adrian.chamberlain@?.com> writes:

> Hi,
> I have a small problem concerning procedure parameter values and variable
> bindings which I would appreciate some input on.
> Example test-suite is attached.
> Basically,
> We have Procedure A which has three parameters 'child', 'parent' and
> 'grandparent'.
> We have procedure B which has two parameters 'child' and 'parent'.
> We call procedure A with the values 'child1', 'parent1' and 'grandparent1'
> i.e.
> call procedure A('child1', 'parent1' 'grandparent1')
> Procedure A in turn calls procedure B as follows:
> call procedure B($(parent), $(grandparent))
> This means of course that procedure B will have the following variable
> bindings:
> 'child'  with value of $(parent)
> 'parent'  with value of $(grandparent)
> The problem here is that this results in the parameter 'child' expanding to
> the value 'grandparent1'  as apposed to 'parent1' !!
> Obviously I need the call to procedure B to pass expanded variable
> values (i.e. the paramters to procedure A)  to avoid this situation.  In otherwords I
> need to force immediate variable expansion within procedure A.
> At present the only way I know how to force immediate variable
> expansion is through the use of the set variable node.
> Greg mentioned some months ago that new syntax variants would be introduced
>  i.e. $!(variable)  and $_(variable).
> $!(variable) would force immediate variable expansion.
> This I presume would allow me to achieve the following in procedure A :
> call procedure B($!(parent), $!(grandparent)), therefore avoiding the introduction
> of set variable nodes and consequently procedure B would have the desired
> bindings:
> 'child' with value of 'parent1'
> 'parent' with value of 'grandparent1'
> Are you still planning to introduce these new syntax variants ?
> Thank you in advance for your help
> Kind Regards
> Adrian

Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876
GF: Gregor Schmid, Karlheinz Kellerer          HRB München 140833