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] Disable components

  • Subject: Re: [QF-Test] Disable components
  • From: "Karlheinz Kellerer\, QFS Support" <support@?.de>
  • Date: Wed, 04 Sep 2013 16:14:11 +0200

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.

Other helpful features for checking test-suite consistency can be found
in the menu Operations->Analyzing

Best regards,

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
> _____________________________________________
> 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


Get the most out of QF-Test - Support directly from the authors
* Training & consulting:
* Phone & email support:

Karlheinz Kellerer
Development & Support

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

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