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] including captured stderr or stdout from SUT scripts in the test report
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,
Greg
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
> Eumetsat-Allee 1
> 64295 Darmstadt
> Tel +49 6151 807-7530
> email michael.theurich@?.int
>
> _______________________________________________
> qftest-list mailing list
> qftest-list@?.de
> http://www.qfs.de/mailman/listinfo/qftest-list
--
Gregor Schmid
E: gregor.schmid@?.de
T: +49 (0)8171 38648-11
F: +49 (0)8171 38648-16
Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Karlheinz Kellerer
HRB München 140833
|
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
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.
