Logo QF-Test

Im Archiv der Mailingliste
wertvolle Antworten finden.

 

Gratis Testen  Download  Kaufen

Thomas Max, QF-Test Training und Support

Tipp für die Recherche in der Mailingliste: Volltextsuche (oben) verwenden.

Thomas Max,
Sr. Software Engineer & Trainer, QFS

2016 bis heute 2015 | 2014 | 2013 | 2012 | 2011 2010 2009 | 2008 | 2007

(ältere Archiveinträge vor 2007 nicht dargestellt, aber in der Suche enthalten)

Mailingliste - Einträge 2007


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] HTML report for enabled/disabled state checks


  • Subject: Re: [QF-Test] HTML report for enabled/disabled state checks
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 10 May 2007 22:16:49 +0200

Hi Hans,

Hans Schwaebli <hans_schwaebli@?.com> writes:

>    Hi Gregor,
>
>
>
>    I ate your Snickers out of frustration (not because QFT), but I will
>    buy you new one. ;-)

No problem, I know that feeling... :-)

>    In the log it is written "Enabled state mismatch Expected enabled
>    state: 'true': Got state: 'false'."
>
>
>
>    This contains no clue what exactly went wrong. Even if I write
>    something in the comment field, it is not shown in the HTML report.
>
>
>
>    If QF Test would include the componenent ID in the HTML report, this
>    would be good. And additionally a screenshot of the disabled/enabled
>    component.

Hmm. A screenshot of just the target component after a failed check is
not a bad idea.

Anyway, are you talking about old or new-style reports? In the
old-style reports you can get the check comment logged by starting it
with a '!'. In the new-style reports, checks are currently more or
less ignored. This is on the TODO for the next medium upgrade. You
should get a screenshot logged, however.

In general the idea is that the report gives you an idea about what
went wrong and the run-log has the detail. In most cases you'll need
to look at the log anyway to find the actual source of the problem.
But I agree that the report could be more helpful in this regard. As
you said, even the component ID would help.

Best regards,
    Greg


--
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876
GF: Gregor Schmid, Karlheinz Kellerer          HRB München 140833



Videos Downloads Dokumentation Kaufen Gratis Testen