(ältere Archiveinträge vor 2007 nicht dargestellt, aber in der Suche enthalten)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [QF-Test] Feature Request
Hi Arnd, thank you for your hints and requests.But let me add some remarks first, because I think most of the features are covered already ;-) Please correct me, if I were wrong.
Regarding 1:Have you used the popup-menu "Locate component" ("Komponente finden") when clicking on a specific node?
Regarding 2:QF-Test 2.2 provides a package "qfs.shutils" in the standard library qfs.qft, perhaps you can make use of those procedures. There is a procedure called "exist", which could be used in your case.
Regarding 3:You could try to set the "Error level" ("Fehlerstufe") of the Catch to "error", then QF-Test will write the error immediately into the run-log and you don't need to re-throw anything. You could also make use of the procedure run-log.logError from qfs.qft, which will write an error into the run-log. This procedure has to be called in the catch-branch again.
he concept of errors of QF-Test won't allow errors to make throwable. If you want to influence the test-flow, you have to use exceptions. I think, that's a key-concept, which we definitely won't change.
Regards, Martin--On Donnerstag, Dezember 20, 2007 13:32:33 +0100 Arnd Bragenheim <arnd@?.de> wrote:
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
-- 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