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] Getting the log Error message in a variable
Hi Aswanth, there is no rc.getLastError message as such, but if you implement a TestRunListener you can read the message from the TestRunEvent in the problemOcurred calls: http://www.qfs.de/qftest/manual/en/tech_testrunlisteners.html#sec_testrunlisteners Best regards, Greg "Seetharaman, Aswanth" <Aswanth_Seetharaman@?.com> writes: > Hi, > > I was writing a listener at the test set level to get the status for each test case and I need to > report to my database with that status of each testcase with the failure reasons. > > To achieve this, is there a similar method like getLastException() to get the Error message > specified in the rc.logError() method. > > For ex : > > If I am logging it like rc.logError(“ This is an Error ”) > > I need to get that string “This is an Error” in a variable. > > How can we achieve this? > > Regards, > > Aswanth Seetharaman, > > BMC Sotware, > > Pune, > > India – 411041 > > Extn – 020 -39875922 > > Mob- 8600677222 > > _______________________________________________ > 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.