List Icon
Archiv Mailingliste

2019 bis Juli 2022  2018  | 2017 2016 2015 | 2014 | 2013

Die Mailingliste ist seit Juli 2022 geschlossen, dient aber weiterhin als Informationsarchiv zu QF-Test.
Wenn Sie aber über Neuerungen zu QF-Test informiert bleiben wollen, können Sie einfach unseren
Newsletter abonnieren

Um aktuell die Informationen zu jeder Release - auch Minor Releases - zu bekommen, können Sie den
RSS-Feed abonnieren oder uns in sozialen Medien folgen.
Alternativ bietet QF-Test auch selbst eine Versionsinformation an.

Eine weitere Informationsquelle ist unser Blog, in dem es aktuelle Beiträge zu allgemeinen Themen, zur Firma QFS und auch diverse "How-Tos" gibt:
Blog abonnieren

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

Re: [QF-Test] rc.LogError method

  • Subject: Re: [QF-Test] rc.LogError method
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Mon, 06 Jun 2016 20:50:54 +0200

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

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

Best regards,

"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

Gregor Schmid

E: gregor.schmid@?.de
T: +49 8171 38648-11
F: +49 8171 38648-16

Quality First Software GmbH |
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer
HRB München 140833