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

Mailing List - Entries of 2012


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

[QF-Test] How to execute a Dependency Cleanup-Node exactly once?(SUT start-stop)


  • Subject: [QF-Test] How to execute a Dependency Cleanup-Node exactly once?(SUT start-stop)
  • From: Henrik Horneber <Henrik.Horneber@?.de>
  • Date: Wed, 22 Feb 2012 16:26:23 +0100

Hi,

regarding the 'cleanup-node': if you run your tests in batch mode, it will trigger the clean-up node after all tests are run.

At least it does for me :-)

Best Regards / Mit freundlichen Grüßen

Henrik Horneber




Von:        Markus Fülle <markusfulli@xxxxxxxxxxxxxx>
An:        qftest-list@xxxxxx
Datum:        22.02.2012 16:16
Betreff:        [RMX:##] [QF-Test] How to execute a Dependency Cleanup-Node exactly once?(SUT start-stop)
Gesendet von:        qftest-list-bounces@xxxxxx




Hi there,

I have one 'testsuite' with several 'test-sets', each containing several 'test-cases'.

I definded a dependency containing a 'preparation-node' (starts the SUT if not already started) and a 'cleanup-node' (shuts down the SUT).

Is there any way to make qftest run the dependency's 'preparation-node' EXACTLY ONCE before running any 'test-set / test-case'  and running the dependency's 'cleanup-node' EXACTLY ONCE after completing  all 'test-set / test-cases' ?

My efforts until now:

Using a reference to this dependency and switching on dependecy inheritance on 'test-set / test-case' nodes obviously does execute the preparation as often as the dependency is inherited. A 'try' in here helps to prevent the SUT from beeing started multiple times and thus 'faking' the wanted behavior 'execute preparation only ONCE'.
On the other side, the 'cleanup-node' NEVER gets executed, until I set the dependency to 'force clean-up', which leaves the cleanup beeing executed each and every time too - though I want it to be executed only once.

What am I missing? Is the dependency mechanism the right way to do this at all?


Thanks und regards,

Markus
_______________________________________________
qftest-list mailing list
qftest-list@xxxxxx
http://www.qfs.de/mailman/listinfo/qftest-list