2018 bis heute | 2017 2016 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] Serialization of Dependencies

  • Subject: Re: [QF-Test] Serialization of Dependencies
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 28 Nov 2007 21:33:16 +0100

Hello Mark,

I guess answering that question is my job... :-)

I'm considering implementing something akin to a 'Call dependency'
node that would let you resolve dependencies from any point in a test.
Perhaps with an option to only roll back the stack up to a given point
without rebuilding it anew.

On the other hand I have not yet been convinced that this is really
necessary. Same for your case. Ask yourself: Why do you need to
restart the application? What's the difference between the
invocations? Let's say it's a parameter for startup. Put that
parameter in a variable and make that variable characteristic for the
"Application started" dependency. That way, if your app is running
with one setting your next 'Test-case' depends on the app being
started with a different setting - meaning the variable now has a
different value, QF-Test will roll back the dependency (i.e. execute
it's Cleanup node which is supposed to stop the application) so that
upon execution of the new Setup it will need to start the app again.

If you really need to stop and restart the app within a single
test-case, move startup and shutdown sequences to procedures which you
can call from the dependency as well as from any other place.

I know, that's not quite the same because it doesn't take care of
proper rollback of the dependency stack.

Further input, anybody?

Best regards,

"Michaelis, Mark" <mark.michaelis@?.com> writes:

>    Hello,
>    I would like to ask you what you would suggest for the following
>    problem concerning dependency linearization:
>    If I got the algorithm in QF-Test right dependencies are linearized in
>    that way that independent dependencies are called in any
>    "non-predictable" order. If I got this idea right I have a problem:
>    I have the following dependencies:
>    ·         Application Started
>    Ensures that the application is started and ready for test. This is the
>    node called most often.
>    ·         Application Stopped
>    This dependency shall ensure that the application is stopped. Example
>    would be to change some configuration files etc.
>    ·         Application Restarted
>    Now I have tests where I need to ensure that the application is
>    restarted from scratch. At least this is the current solution I have in
>    mind. To do so I have to ensure the application is stopped and then
>    started again. This can of course be done moving the stopped/started
>    preparation nodes to procedures I will call. But the solution I think
>    of would be:
>    o    Dependency: Application Restarted
>    §  Sequence
>    ·         Depend on Application Stopped
>    ·         Depend on Application Started
>    I. e. I would like to allow the Sequence Node as direct element below
>    the Dependency node with the effect that Application Stopped dependency
>    is ensured to be put in front of Application Started during
>    linearization.
>    What do you think? Does this make sense? Is it worth a feature request?
>    Or do I treat the dependencies wrong?
>    Any hints welcome.
>    Kind Regards
>    *** Mark
>    --
>    Mark Michaelis
>    Software Engineer Quality Assurance
>    CoreMedia
>    Ludwig-Erhard-Str. 18
>    20459 Hamburg, Germany
>    [1]www.coremedia.com
>    --------------------------------------------------------
>    CoreMedia AG
>    Executive Board: Sören Stamer (CEO), Dr. Klemens Kleiminger (CFO)
>    Supervisory Board: Prof. Dr. Joachim Schmidt (Chairman)
>    Trade Register: Amtsgericht Hamburg, HR B 76277
>    --------------------------------------------------------
> Verweise
>    1. http://www.coremedia.com/
> _______________________________________________
> qftest-list mailing list
> qftest-list@?.de
> http://www.qfs.de/mailman/listinfo/qftest-list

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