Mailing list - Entries of 2005

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

Re: [qftestJUI] can't catch ComponentNotFoundException in SUT script

  • Subject: Re: [qftestJUI] can't catch ComponentNotFoundException in SUT script
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Wed, 30 Mar 2005 21:52:02 -0000

Hi Ido,

you really have a talent for finding problems. I think you've got the
right job :-)

In this case there are two problems: ComponentNotFoundException isn't
imported by default in the SUT script context (which it should) and
the inherent complexity and threading weirdness of rc.getComponent
hide the exception that would show that ComponentNotFoundException is
actually undefined.

Both will be fixed with the next maintenance release.

For now, please add

# Temporary fix, should be removed in the future
from de.qfs.apps.qftest.client import ComponentNotFoundException

at the top of your script, or better yet, put this in a separate SUT
script node right after connecting to the client.

Best regards,

Ido Kofler <ido.k@?.com> writes:

> Hi all,
> in my SUT script i try to catch ComponentNotFoundException with the
> following jython script:
> try :
>     rc.getComponent("<component name>")
> except ComponentNotFoundException :
>     rc.logError(" message")
> each time i run this script, it failed and throw message that
> "component could not be determined",
> does anyone know why the script that i use don't catch it?
> 10x
> Ido

Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH           
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876