2017 up to now  | 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 2015


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

Re: [QF-Test] Logging effective waiting time when executing Check nodes with defined time out?


  • Subject: Re: [QF-Test] Logging effective waiting time when executing Check nodes with defined time out?
  • From: arulraj.savariraj@?.com
  • Date: Mon, 28 Sep 2015 11:20:49 +0200

Hello Ralf,

I would suggest you to use the simple Loop Structure instead of using waiting time.

For example , if you want to continue your test once the Button 1 is enabled , you can use the below code

----------------------------------------------------------------------------------------------------------------
Set variable Temp = false
Loop (100) (QF TEST ID as LOOP1)

        Check boolean (Check Type Identifier as 'enabled' , variable for result as 'Temp' and component Id as Button 1)
        If ('$(Temp)'=='true')
                Break LOOP1
-----------------------------------------------------------------------------------------------------------------

I am checking the state of the Button 1 using Check Boolean. Once the button is enabled , pointer will break the loop and come out of it.

Merits:

If you use waiting time as 2 second , pointer will wait up to 2 seconds even the button is enabled in 1 second and then it will continue the execution. But if you use the above loop, it will exit once the button is enabled. Also if the button takes more than 2 second, that is also handled in this loop.

Hope this will help you.

Thanks

Arul S
               


[QF-Test] Logging effective waiting time when executing Check nodes with defined time out?

(Internet)
ralf.pfiszter
To: qftest-list

09/28/2015 10:52 AM

Sent by : qftest-list-bounces@?.de







Hi,

my issue is that our test environment has sometimes performance issues which slows down the test execution and increases the response times within the tested SWT application.
To mitigate this I added some check nodes to the szenarios to check the enabled status of a specific button to know when to continue.

I now want to get better figures about the response times - so I want to log the effective waiting time for single Check nodes into the protocol.

Can someone please point me to a way how I can achieve this in a simple and effective manner?

I am somehow still a QFTest novize so I am happy to get an answer describing the steps in a certain detaillation.

Thank you in advance
Ralf

_______________________________________________
qftest-list mailing list
qftest-list@?.de
https://www.qfs.de/mailman/listinfo/qftest-list

This message and any attachments (the "message") is
intended solely for the intended addressees and is confidential.
If you receive this message in error,or are not the intended recipient(s),
please delete it and any copies from your systems and immediately notify
the sender. Any unauthorized view, use that does not comply with its purpose,
dissemination or disclosure, either whole or partial, is prohibited. Since the internet
cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS
(and its subsidiaries) shall not be liable for the message if modified, changed or falsified.
Do not print this message unless it is necessary,consider the environment.

------------------------------------------------------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le "message")
sont etablis a l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
merci de le detruire ainsi que toute copie de votre systeme et d'en avertir
immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de
ce message qui n'est pas conforme a sa destination, toute diffusion ou toute
publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer
l'integrite de ce message electronique susceptible d'alteration, BNP Paribas
(et ses filiales) decline(nt) toute responsabilite au titre de ce message dans l'hypothese
ou il aurait ete modifie, deforme ou falsifie.
N'imprimez ce message que si necessaire, pensez a l'environnement.