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 2013


[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: Cojanu Cosmin <Cosmin.Cojanu@?.com>
  • Date: Thu, 19 Dec 2013 08:50:52 +0000

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.