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
our obtenir des informations à jour sur chaque version - y compris les versions mineures - vous pouvez
nous pouvez vous abonner au flux RSS ou nous suivre sur les médias sociaux.
Alternativement, QF-Test fournit également des informations sur la version elle-même.
Une autre source d'information est notre blog, qui contient des articles actuels sur des thèmes généraux, sur l'entreprise QFS et aussi divers "how-tos", veuillez vous
ABonner au Blog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] rc.LogError method
Hello Hardik, I'm afraid that's a common misapprehension, not least because we often ask users to add a little logError script for analyzing support issues. So let me explain... The call rc.logError just logs an error. In case of an error, regardless whether it comes from a script or from other nodes, QF-Test takes screenshots. So normally you get a screenshot for your error logs. However, too many screenshots can quickly exhaust available memory, so they are only taken for the first few errors, except in cases of split run-logs where the default is to start again from 0. This is all configurable. Please see the options "Count screenshots individually for each split log", "Create screenshots of the whole screen" and "Create screenshots of the whole screen" at https://www.qfs.de/qftest/manual/en/opt_log.html#opt_maximumscreenshotsperlog for detailed information. However, you normally don't need to change those options. To log a screenshot independent of the error count, best use the procedure qfs.screenshots.logScreenshot from our standard test-suite library qfs.qft: https://www.qfs.de/fr/bibliotheque-standard.html#qfs.run-log.screenshots.logScreenshot Best regards, Greg "Patel, Hardik" <Hardik.Patel@?.com> writes: > Dear Team, > > Based on my understanding rc.LogError method captures the screenshots. Somehow it’s > just displaying message in the Run Log – HTML report as STOP but no screenshots. I > couldn’t find proper documentation around this method as well. I need to use this > method inside the catch and capture the error screenshot. > > Thanks & Regards, > > Hardik Patel > > Senior QA| EPG > > Experian | Rugby > > Information in this e-mail and any attachments is confidential, and may not be > copied or used by anyone other than the addressee, nor disclosed to any third party > without our permission. There is no intention to create any legally binding contract > or other binding commitment through the use of this electronic communication unless > it is issued in accordance with the Experian Limited standard terms and conditions > of purchase or other express written agreement between Experian Limited and the > recipient. Although Experian has taken reasonable steps to ensure that this > communication and any attachments are free from computer viruses, you are advised to > take your own steps to ensure that they are actually virus free. > > Experian Ltd is authorised and regulated by the Financial Conduct Authority. > Companies Act information: Registered name: Experian Limited. Registered office: The > Sir John Peace Building, Experian Way, NG2 Business Park, Nottingham, NG80 1ZZ, > United Kingdom. Place of registration: England and Wales. Registered number: 653331. > > _______________________________________________ > 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
|
1. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.