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] 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/en/standard-library.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