2018 up to now | 2017 | 2016 | 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] Feature Request

  • Subject: Re: [QF-Test] Feature Request
  • From: "Annie Connell" <anne.connell@?.com>
  • Date: Thu, 20 Dec 2007 13:46:18 -0000

Title: Message
I am about to have a similar need to that outlined in point b) below.
On behalf of one of our users, I will need to write a test that checks a special flat file that is exported from our database.  I need to check that the file has been produced, on the appropriate trigger, and I also need to check its content.
I can do this by having a 'model' file at a known location, which looks exactly like the file that should be produced; I am wondering how, within QFTest, I can check that the file exists, and run a compare to see it matches the 'model'.
Any suggestions would be gratefully received.

Anne Connell
HPD Software Limited
Tel: + 44 (0) 20 8780 6800
Fax: + 44 (0) 20 8780 6801/5
mailto anne.connell@?.com

-----Original Message-----
From: qftest-list-bounces@?.de [mailto:qftest-list-bounces@?.de] On Behalf Of Arnd Bragenheim
Sent: 20 December 2007 12:33
To: qftest-list@?.de
Subject: [QF-Test] Feature Request

Dear QF-Team!


We would like to request three features:


a) When we select a node, (check for example) and press the button “ ID der Komponente” (german version), a separate window pops up, which shows the location of the component inside the whole component tree.

We would like to jump from that window into the real tree, so that we can rename or copy the component there.

It is inconvenient to navigate through the tree manually, especially because the window must be shut before and so the path only exists in the memory of the User…


b) Perhaps this feature is already there but we have not found it yet… When our SUT generates files or folders, we would like QF-Test to check for the absence/presence of these files. By using a shell command or an external program, we can surely search for files and store the result somewhere, but we would prefer QF-Test to manage this internally for protocoll etc... So a “File-Presence-Checker”-node or something like that would be nice. Maybe even a “File-Content-Checker”.


I don’t know if it is realistic, but can you get results from the shell-commands? Then it would be able to use these results for If etc…


c) When we have a tree in our SUT, and we wanna check the absence of nodes, at the moment we try checking the name of the node, this should fail. So in the catch-part, we throw an Exception a la “This Exception was thrown instead of an error”. Not really important, but more elegant would be the ability to throw errors. Maybe this is easiliy done.



Thanks for your attention, merry Christmas to everyone,



Arnd Bragenheim