The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
But if you want to stay informed about news about QF-Test, you can simply
Subscribe to Newsletter
To get up-to-date information about each release - including minor releases - you can
subscribe to the RSS feed or follow us on social media.
Alternatively, QF-Test also provides release information itself.
Another source of information is our blog, where there are current articles on general topics, on the company QFS and also various "how-tos"
subscribe to blog
[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?
Hello Ralf, execution time of the check is logged in the run-log just as for every other node, both as real time and execution time (real time minus artificial overhead like explicit waits). If you're looking for something more explicit that will also make it into the report, you can wrap the check into a 'Sequence with time limit' node, cf: https://www.qfs.de/qftest/manual/en/sequences.html#step_TimeConstrainedSequence Best regards, Greg Ralf Pfiszter <ralf.pfiszter@?.at> writes: > Hi Arul, > > maybe there happened a misunderstanding regarding my question. > > I already use a Check node instead of defining a hard timeout - which covers from a functional > perspective that loop you mentioned. > From what I understand from the manual and got confirmed in a thread answer: "the Check node will > wait until the check succeeds and then continue immediately" - or alternatively it continues when > the defined wait time is reached. > > My question was: does there exist a feature to log the effective time the Check node waited during > the test execution, i.e. the time until the check succeeds or the wait time is reached? > One idea is to add appropriate SUT scripts before and after the Check node - but maybe there is a > more pretty solution I am not aware of? > > Best regards, > Ralf > > Am 2015-09-28 um 11:20 schrieb arulraj.savariraj@?.com: > > 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. > > _______________________________________________ > qftest-list mailing list > qftest-list@?.de > https://www.qfs.de/mailman/listinfo/qftest-list -- Gregor Schmid E: gregor.schmid@?.de T: +49 8171 38648-11 F: +49 8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer HRB München 140833
|