List Icon
Mailing list Archive

2019 up to July 2022 | 20182017  |  2016  2015 2014 | 2013

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]

[QF-Test] Encoding in Comments


  • Subject: [QF-Test] Encoding in Comments
  • From: Nedvěd, Marek <m.nedved@?.de>
  • Date: Wed, 10 Aug 2016 14:30:43 +0000

Hello QF-Test people,

We have started using testlink integration to export the test cases into the QF-Test. We are writing our test cases in german. The general description appears in the Comment section of the Qf-test nodes.

 

The problem is, that when we later try to run the tests on our Jenkins the html report shows the comments with replacements symbols (?) instead of umlaut symbols. Strangely, the names of the nodes (test set, cases, steps,…) are displayed correctly with proper encoding.

 

I am convinced that it happens only on the Jenkins, but I have no Idea what might be the cause. Generating the html report just from the studio or batch has the correct encoding also in the comments. Has anyone encountered this behavior? Is there a way to fix this?

 

Cheers

Marek N
edvěd