List Icon
Archive de la liste de diffusion

La liste de diffusion est fermée depuis juillet 2022, mais sert toujours d'archive d'informations sur QF-Test.
Cependant, si vous souhaitez rester informé des nouveautés concernant QF-Test, vous pouvez simplement vous abonner à la newsletter :
abonner à la newsletter 


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

Re: [QF-Test] How to set a variable from a Break in a loop?


  • Subject: Re: [QF-Test] How to set a variable from a Break in a loop?
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Thu, 19 Dec 2013 15:49:37 +0100

Hi Cosmin, hi Rick,

there's also a very nice but little known feature of the QF-Test
'Loop' node which I copied from Python's "for" loop: You can add an
'Else' node to the bottom of the 'Loop' which will be executed if and
only if the 'Loop' is not exited prematurely via 'Break', i.e. exactly
in the case when a search fails.

Best regards,
    Greg

Cojanu Cosmin <Cosmin.Cojanu@?.com> writes:

> Hi Rick,
>
> You can set a local/global variable before the Break node by using:
>
> - “Insert Node -> Miscellaneous -> Set Variable”
>
> or
>
> - Insert an SUT/Server Script node that contains something like rc.setLocal(‘variable_name’,
> ‘value_to_set’)
>
> This can be checked after in an “If” to execute the specific steps in case the row was selected or
> not.
>
> Hope this helps.
>
> Regards,
>
> Cosmin cojanu
>
> From: qftest-list-bounces@?.de [mailto:qftest-list-bounces@?.de] On Behalf Of Rick Brasche
> Sent: Thursday, December 19, 2013 2:16 AM
> To: 'qftest-list@?.de'
> Subject: [QF-Test] How to set a variable from a Break in a loop?
>
> Good morning/evening QFS users, Martin and/or Gregor:
>
> In my suite I have a Loop that runs to check two columns of text in a table for a single row that
> matches. The Loop runs until all rows are checked and as soon as it finds the row matching
> conditions it then runs a Break and clicks on that current row.
>
> The problem is, sometimes for a given table, there is no row that matches. In that case, QFS
> continues on to the next available procedure, which is not the correct behavior for our business
> process.
>
> What we want to happen, is to have at the point of the Break, a variable to be assigned. That
> variable then to be called on later to choose what step the suite moves onto next.
>
> We don’t want an error thrown, we want it to move to a separate procedure if the conditions we
> assign are not met than if they were.
>
> Thanks in advance for any help you can provide.
>
> Rick Brasche,
>
> Information Systems Business Process Automation.
>
> ------------------------------------------------------------------------------------------------------------------------------
>
> “The difficult we do immediately, the impossible just takes a bit longer.” – US Navy SeaBees.
>
> NOTICE: This email message and/or its attachments may contain
> information that is confidential or restricted. It is intended only for
> the individuals named as recipients in the message. If you are NOT an
> authorized recipient, you are prohibited from using, delivering,
> distributing, printing, copying, or disclosing the message or content to
> others and must delete the message from your computer. If you have
> received this message in error, please notify the sender by return
> email.
>
> _______________________________________________
> qftest-list mailing list
> qftest-list@?.de
> http://www.qfs.de/mailman/listinfo/qftest-list

--
Gregor Schmid

E: gregor.schmid@?.de
T: +49 (0)8171 38648-11
F: +49 (0)8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Karlheinz Kellerer
HRB München 140833