(ä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] Creating a CSV file that contains results.
Hi Derrik, as of today you need to implement this yourself. However, we've got plans for opening an internal API that will let you register a kind of TestListener that will be notified about entry/exit to/from a node and about warnings/errors/exceptions during a test-run. The basics are pretty simple, but, as often, the problems are hard to get right. What information exactly do we need to provide about the currently executing test-node? Obviously we don't want to open the internal representation as there are over 50 different kinds of nodes with a huge amount of associated classes. But would, for example, the text representation of a node as shown in the tree suffice? Opinions welcome. Best regards, Greg "Derrik Ammons" <dammons@?.COM> writes: > We have a system that takes a simple CSV file of results and other > values for automated reporting. > > > > Does a Test Case node know about itself, like it's name, it's run > time, the pass/failure state, etc. so that at the end of the Test > Case, I can write the parameters to a CSV file? I thought this may be > easier than parsing the run log. The other way would be to declare > variables for each value I need to write to the CSV file and take care > of it myself, however, why waste memory and cpu cycles if the values > are already taken care of within the Test Case. > > > > Thanks, > > Derrik -- Gregor Schmid Gregor.Schmid@?.de Quality First Software GmbH http://www.qfs.de Tulpenstr. 41 Tel: +49 8171 919870 DE-82538 Geretsried Fax: +49 8171 919876 GF: Gregor Schmid, Karlheinz Kellerer HRB München 140833