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.
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] Encoding in Comments

  • Subject: Re: [QF-Test] Encoding in Comments
  • From: "Yann Spoeri, QFS" <yann.spoeri@?.de>
  • Date: Mon, 15 Aug 2016 11:45:07 +0200

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 (&auml; instead of ä, &ouml; instead of ö, &uuml; instead of ü, &szlig; 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.


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?


Marek Nedvěd

qftest-list mailing list