2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012

Mailing List - Entries of 2013


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

[QF-Test] Disable components


  • Subject: [QF-Test] Disable components
  • From: Henrik Horneber <Henrik.Horneber@?.de>
  • Date: Tue, 3 Sep 2013 14:16:05 +0200

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@xxxxxxxx
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.