2017 bis heute 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] Generic Ids in Test Suites and Version Control


  • Subject: Re: [QF-Test] Generic Ids in Test Suites and Version Control
  • From: "Michaelis, Mark" <mark.michaelis@?.com>
  • Date: Tue, 24 Apr 2007 11:24:51 +0200

Hello Greg,

thanks for the hint to the import function of qftest. I was not aware of that. It might be helpful in common cases. But it also does not solve all conflicts. Especially if on one branch procedures/components exist which got removed on the other branch. Importing will make those reappear.

About components I am glad that I keep them in separate suites. I hope to get around strong integration conflicts. But after all I think this topic is not easy to address. At least qftest is better to be handled in VCS than other GUI Test software I know of.

Kind Regards,
	Mark

> -----Original Message-----
>
> Hello Mark,
>
> this kind of ID conflict with automatic IDs starting with an
> underscore is no problem. As you saw, QF-Test is able to cope.
>
> However, you may get conflicts for component IDs when merging
> test-suites textually. Here it is better to use QF-Test's import
> function. Otherwise you'll have to resolve the ID conflict manually.
>
> Best regards,
>     Greg
>
> "Michaelis, Mark" <mark.michaelis@?.com> writes:
>
> >    Hello,
> >
> >    I just had the problem to integrate changes from one
> branch in the VCS
> >    to another. In both versions there have been new
> procedures added to
> >    the test-suite, so I had:
> >
> >      * In Branch 1 a procedure "branch1" got added and in
> the QFT file it
> >        got id "_1"
> >      * In Branch 2 a procedure "branch2" got added and it
> got id "_1",
> >        too
> >      * I want to integrate procedure "branch1" from Branch
> 1 to Branch 2;
> >        the VCS suggested:
> >
> >      * Procedure "branch1" with id "_1" and
> >      * Procedure "branch2" with id "_1"
> >
> >    I was puzzled by the fact that there are now duplicate
> ids. I tested a
> >    little bit with a dummy test-suite and it seems that
> qftest is able to
> >    handle this duplicate id... it runs quite well but on
> saving again
> >    qftest seems to reorganize the ids so that e. g.
> "branch2" procedure
> >    will get id "_2" after saving.
> >
> >
> >
> >    I just would like to ask if it is safe to assume that
> qftest handles
> >    these duplicate ids in a correct manner or is it useful
> to set ids
> >    manually next time.
> >
> >
> >
> >    Kind Regards
> >
> >        Mark

--
Mark Michaelis
Software Engineer Quality Assurance

CoreMedia
Ludwig-Erhard-Str. 18
20459 Hamburg, Germany
www.coremedia.com

--------------------------------------------------------
Any content, anywhere, in a trusted universe:
CoreMedia CMS, CoreMedia DRM, CoreMedia Mobile TV
--------------------------------------------------------
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

--------------------------------------------------------