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] including captured stderr or stdout from SUT scripts in the test report

  • Subject: Re: [QF-Test] including captured stderr or stdout from SUT scripts in the test report
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Wed, 02 Jul 2014 10:00:12 +0200

Hello Michael,

you can include arbitrary messages in the report by calling
rc.logMessage with the report parameter set to true.

And you have access to the output of a process via the variable
${qftest:client.output.<name>} or, preferably, in a Server script via

rc.lookup("qftest", "client.output.<name>", false)

The argument false for the parameter expand of the rc.lookup method is
useful here to prevent QF-Test from trying to expand $(...)
expressions that might be contained in the client output.

Bringing all of this together in a Jython 'Server script' node:

client = rc.lookup("client")
output = rc.lookup("qftest", "client.output.%s" % client, false)
rc.logMessage("Output from client %s:\n%s" % (client, output), report=true, nowrap=true)

Note: The nowrap parameter produces better results for this kind of
output in the report as it results in preformatted text that doesn't
wrap the lines.

Best regards,

Michael Theurich <Michael.Theurich@?.int> writes:

> Hi,
> In our tests, a lot of importance is given to check the output files generated by the SUT at the
> end of each test. This is done by external shell scripts, which have already been developed
> earlier, I don’t really want to reimplement them as SUT or server scripts. In case of errors, the
> stderr or stdout contains valuable hints. This is captured nicely in the QFT logs. Is there a way
> to also include this somehow in the generated reports (similar to the screenshots) in case of
> failed tests? If not, is there a plan to include this in future versions?
> Thanks,
> Michael
> ---------------------------------------------------------------------------------
> Michael Theurich
> Monitoring Application Tools SW Engineer
> Telespazio VEGA Deutschland GmbH
> Provision of Engineering Support Services
> Eumetsat-Allee 1
> 64295 Darmstadt
> Tel +49 6151 807-7530
> email michael.theurich@?.int
> _______________________________________________
> qftest-list mailing list
> qftest-list@?.de

Gregor Schmid

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

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