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] Encoding in Comments
Hello Marek,
QF-Test is encoding it's HTML report by using ISO-8859-1 as encoding. Unfortunately, when Jenkins is serving documents it is specifying UTF-8 as
encoding in the HTTP header. This is why the german special characters are displayed wrongly.
This is no problems in node names (test set, cases, steps, ...) since QF-Test is there replacing these special characters by there XML-escaped
representations (ä instead of ä, ö instead of ö, ü instead of ü, ß instead of ß and so on).
You may manually tell the browser, that it should use ISO-8859-1 for document interpretation. E.g. in Firefox you can do this via the View menu
-> Text Encoding -> Western.
Alternatively, if you don't use any HTML tags in the comment section, disable the "Pass HTML tags through" option while generating your HTML
reports. QF-Test is then - also in comments - replacing the special characters by there XML-escaped representation.
Greetings,
Yann
Am 10.08.2016 um 16:30 schrieb Nedvěd, Marek:
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 Nedvěd _______________________________________________ qftest-list mailing list qftest-list@?.de https://archive.qfs.de/mailman/listinfo/qftest-list
|
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.
