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]

Re: [QF-Test] Antwort: Re: Disable components


  • Subject: Re: [QF-Test] Antwort: Re: Disable components
  • From: "Karlheinz Kellerer\, QFS Support" <support@?.de>
  • Date: Fri, 06 Sep 2013 14:30:44 +0200

Hi Henrik,

Henrik.Horneber@?.de writes:

> Hi,
>
> thank you for your reply.
>
> Analyzing was new to me, I already found some inconsistencies in one
> of our suites. Great!

:)

>
> Nevertheless I'm still kind of disappointed ;-) that disabling of components does not have any
> effect.
>
> Same thing for a breakpoint on a component or a marker on a component - none of that has any
> difference on the actual test-run.
>
> I'm thinking that any of those (disabling, marking or setting a break point) would be a
> conceptually simple but powerful feature,

I have to confess that sounds convincing. We have discussed this internally and
came to the same result. It's on the agenda now for QF-Test version 4 :).

Thanks again for your input on this.

Best regards,
    Karl


>
> Best Regards / Mit freundlichen Grüßen
>
> Henrik Horneber
> Continental AG, IT R&D Tires
> Software Engineering
> Email: henrik.horneber@?.de
> Phone: +49-511-976 / 41 93 9
> Fax:   +49 511 976 36723
>
> http://www.continental-corporation.com
> _____________________________________________
> Continental Reifen Deutschland GmbH, Vahrenwalder Str. 9, D-30165 Hannover
> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Nikolai
> Setzer; Geschaeftsfuehrer/Managing Director: Bernd Guenther, Burkhardt
> Koeller
> Sitz der Gesellschaft/Registered Office: Hannover,
> Registergericht/Registered Court: Amtsgericht Hannover HRB 204239,
> USt.-ID-Nr./VAT-ID-No. DE264920698
> _____________________________________________
> Proprietary and confidential. Distribution only by express authority of
> Continental AG or its subsidiaries.
>
> Von:        "Karlheinz Kellerer\, QFS Support" <support@?.de>
> An:        Henrik Horneber <Henrik.Horneber@?.de>
> Kopie:        "qftest-list\@qfs.de" <qftest-list@?.de>
> Datum:        04.09.2013 16:24
> Betreff:        Re: [QF-Test] Disable components
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>
> Hi Henrik,
>
> In difference to all other nodes, disabling of component nodes doesn't
> have any real effect (beside changing the color).
>
> Therefore the only way of finally checking is to actually remove the
> unused components and re-run the tests. A backup of the test-suite is
> recommended before performing mass changes like removing unused
> components, of course.
>
> QF-Test helps finding, marking and removing of unused components.
>
> http://www.qfs.de/qftest/manual/en/user_components.html#sec_NE15
>
> Other helpful features for checking test-suite consistency can be found
> in the menu Operations->Analyzing
>
> Best regards,
>    Karl
>
> Henrik Horneber <Henrik.Horneber@?.de> writes:
>
>> Hi,
>>
>> I've found no explanation in the manual, so maybe someone on the list can help me out:
>>
>> What does disabling a component via context menu do, exactly?
>>
>> Since 'mark unused components' not only marks but also disables components, I was expecting it
> to
>> work as a sort of soft delete.
>>
>> I.e. you could use this to mark components QF Test thinks are unused, then run the suite to make
>> sure they really are unused (and not indirectly passed somewhere as a variable string, for
>> example).
>>
>> But when I disable components which ARE used, the tests still work fine.
>>
>> Disabling does not seem to affect anything except the way the component is displayed in the
>> component tree.
>>
>> Any hints? What am I missing?
>>
>> How else can I test-run deletion of unused components?
>>
>> Best Regards / Mit freundlichen Grüßen
>>
>> Henrik Horneber
>> Continental AG, IT R&D Tires
>> Software Engineering
>> Email: henrik.horneber@?.de
>> Phone: +49-511-976 / 41 93 9
>> Fax:   +49 511 976 36723
>>
>> http://www.continental-corporation.com
>> _____________________________________________
>> Continental Reifen Deutschland GmbH, Vahrenwalder Str. 9, D-30165 Hannover
>> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Nikolai
>> Setzer; Geschaeftsfuehrer/Managing Director: Bernd Guenther, Burkhardt
>> Koeller
>> Sitz der Gesellschaft/Registered Office: Hannover,
>> Registergericht/Registered Court: Amtsgericht Hannover HRB 204239,
>> USt.-ID-Nr./VAT-ID-No. DE264920698
>> _____________________________________________
>> Proprietary and confidential. Distribution only by express authority of
>> Continental AG or its subsidiaries.
>>
>> _______________________________________________
>> qftest-list mailing list
>> qftest-list@?.de
>> http://www.qfs.de/mailman/listinfo/qftest-list

--
_______________________________________________________________

Get the most out of QF-Test - Support directly from the authors
* Training & consulting: www.qfs.de/en/qftest/training.html
* Phone & email support: www.qfs.de/en/qftest/support.html
_______________________________________________________________

Karlheinz Kellerer
Development & Support

E: support@?.de
T: +49 (0)8171 38648-20
F: +49 (0)8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Karlheinz Kellerer
HRB München 140833