Logo QF-Test

Finding valuable answers
in the Mailing List Archive.

 

Free Trial  Download  Buy

Thomas Max, QF-Test training and support

Use the full-text search on our web site to find helpful tips on the mailing list.

Thomas Max, 
Sr. Software Engineer & Trainer, QFS

2016 up to now | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2007


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

Re: [QF-Test] Best Practice Question for Interactive Test Dispatcher/ unable to search


  • Subject: Re: [QF-Test] Best Practice Question for Interactive Test Dispatcher/ unable to search
  • From: Martin Moser <martin.moser@?.de>
  • Date: Fri, 13 Jul 2007 13:07:54 +0200

Hi David,

you can also post the whole path of the test-suite containing the test-case
to the bug details. As a test-case is also identified by
"file-Name#[TestSet].TC-Name", this approach could also be beneficial for
finding test-cases.

Regards,
Martin

--On Dienstag, Juli 10, 2007 14:09:50 -0400 David_Downey@?.com wrote:

When a bug is found via qftest we are making the test id the id of the
bug  from our bug tracking system.  Due to our distributed setup, we have
one  master suite that calls a few/many/all test suites.  The issue: when
a  developer goes to find one of the test cases that contains a bug fix
you  can't just simply go to the master suite and search for the id,
because it  will only see the what is in the master suite (which isn't
much).

One idea we came up with was some kind of interactive test dispatcher or
ITD (patent pending) :)
        There is a separate test suite called interactive test
dispatcher.   The test begins with an interactive variable for the
developer to input  the bug id.  Then there is an if statement created
for every instance  where a bug id was used for a test id.  This approach
accomplishes the  task but doesn't seem like the most ideal approach.

Does anyone have any suggestions on a more efficient way to allow the
developers to find and run test cases that apply to bugs?

David A. Downey
Software Quality Assurance Analyst
BD Technologies
919-597-6523

-----------------------------------------
*******************************************************************
IMPORTANT MESSAGE FOR RECIPIENTS IN THE
U.S.A.:
This message may constitute an advertisement of
a BD group's products or services or a
solicitation of interest in them. If this is
such a message and you would like to opt out of
receiving future advertisements or
solicitations from this BD group, please
forward this e-mail to optoutbygroup@?.com.
*******************************************************************
This message (which includes any attachments)
is intended only for the designated
recipient(s).  It may contain confidential or
proprietary information and may be subject to
the attorney-client
privilege or other confidentiality protections.
 If you are not a designated recipient, you may
not review, use, copy or distribute this
message. If you received this in error, please
notify the sender by reply e-mail and delete
this message. Thank you.
*******************************************************************
Corporate Headquarters Mailing Address: BD
(Becton, Dickinson and Company) 1 Becton Drive
Franklin Lakes, NJ 07417 U.S.A.
*******************************************************************



--
Martin Moser                           martin.moser@?.de
Quality First Software GmbH            http://www.qfs.de
Tulpenstr. 41                          Tel: +49 8171 919874
DE-82538 Geretsried                    Fax: +49 8171 919876
GF: Gregor Schmid, Karlheinz Kellerer  HRB München 14083



Videos Downloads Documentation Buy Free Trial