The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
If you want to stay informed about news about QF-Test, you can simply subscribe to our newsletter:
Subscribe to Newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] testsuite name in JUnit report very long
Hello Bernhard,
I looked into this to see if the command line argument -sourcedir
makes a difference. As it turns out it doesn't.
Of course, one possibility would be post-processing the Junit Report
to remove the path.
And you cold modify the XSLT stylesheet report_junit.xsl and place the
modified copy into the directory .../qftest/report (which you need to
create). It's quite tricky to get right though and I wonder whether
it's worth it in case this is only for cosmetic reasons.
Best regards,
Greg
Bernhard Schmitt <bernhard.schmitt@?.de> writes:
> Hello,
>
> when I create a Junit Report with
> qftest -batch -genreport -report.junit reports\junit\publish -report.warnings true reports\qrz
> the testsuite name contains the suite with the absolute path:
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <testsuite errors="0" failures="9" hostname="XYZ" name="E:/Automaten/
> workspace/EnvMon /testsuites/wrapper/TestBench_Wrapper_qft" tests="16"
> time="2275.451"
>
> This full suite name is displayed in Jenkins in the mask 'Test
> Results'. Is it possible to report only the suite name without
> absolute path?
>
> BR
>
> Bernhard
--
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
|
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.
