On 2010-03-13, Clark Archer <clark.arc...@gmail.com> wrote: > On Tue, Mar 9, 2010 at 11:19 PM, Stefan Bodewig <bode...@apache.org> wrote:
>> Hi Clark >> On 2010-03-09, Clark Archer <clark.arc...@gmail.com> wrote: >>> coded up a HistoryRecorder which builds a simple text file >>> containing a history of up to the last 100 executions for each test >>> class/suite. I track pass/fail and execution time for each test >>> class and update the history file at the end of each <junit /> task. >> This sounds interesting. Despite all the hate XML gets it may be a more >> suitable format, though. You could add more structured data and create >> all sorts of reports later. An alternative would be JSON or any other structured format, of course. > I don't have anything against XML (in particular), but I went with a > text file because I only had a little time to work on it last weekend > and I don't know the various XML APIs well. They can be intimidating and there are a few tradeoffs to consider. E.g. if the file gets large, DOM isn't really an option. > This file has to be read at the beginning of each test run (or batch) > and then updated at the end of the run. Are you updating the file in one operation or are you doing this once per test? A per test operation would certainly be more work in an XML case. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
