I started using SqlUnit a few weeks ago (version 1.8). It is a very helpful tool!!
We use similar JUnit extensions for http testing and convert the output via xsl to nice html pages.
Since SqlUnit writes to STDERR only, we can't do any of this (there is no xml output).
Are there any plans to use regular ant BuildListeners/ Loggers to capture the sqlunit output rather than always writing it to STDERR?
Jan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made it use a file if an optional attribute logfile for the sqlunit tag is set. Its going into version 2.2 (trying to release today, lets see). I thought of using the BuildListener with DefaultLogger but there may be some problems with doing it, I am going to look some more and get back to you.
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thought some more about this, and I am going to roll back my logfile changes in favor of your idea of using a BuildLogger. Also I am going to make these changes more in line with James's patch to let clients other than the sqlunit task run the tests. I was thinking of making the release 2.2 today, but I will push it back a few days so I can get these changes in.
Thanks for the suggestion and I am glad you like SQLUnit :-). I will let you know when I am done with the changes you suggested.
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thanks for the quick reaction.
I am thinking about fixing the standard ant <record> task. This way I can get to the SQLUnit results in xml, once it uses the buildloggers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SQLUnit uses the Ant BuildLogger (specific subclass specified by -logger, not sure if its also a project property). Using the <record> task will actually remove any need for using the <sqlunit> logfile attribute, which also uses the BuildLogger for logging now.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
not using the sqlunit/@logfile attribute was my goal anyway ;)
I wanted to have the choice of BuildLogger, so that I can control the output format etc.
Thanks for all your hard work and keeping up with the requests. I havaen't checked out your latest builds but I'll do this ASAP.
Jan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I started using SqlUnit a few weeks ago (version 1.8). It is a very helpful tool!!
We use similar JUnit extensions for http testing and convert the output via xsl to nice html pages.
Since SqlUnit writes to STDERR only, we can't do any of this (there is no xml output).
Are there any plans to use regular ant BuildListeners/ Loggers to capture the sqlunit output rather than always writing it to STDERR?
Jan
I made it use a file if an optional attribute logfile for the sqlunit tag is set. Its going into version 2.2 (trying to release today, lets see). I thought of using the BuildListener with DefaultLogger but there may be some problems with doing it, I am going to look some more and get back to you.
-sujit
Hi Jan,
Thought some more about this, and I am going to roll back my logfile changes in favor of your idea of using a BuildLogger. Also I am going to make these changes more in line with James's patch to let clients other than the sqlunit task run the tests. I was thinking of making the release 2.2 today, but I will push it back a few days so I can get these changes in.
Thanks for the suggestion and I am glad you like SQLUnit :-). I will let you know when I am done with the changes you suggested.
-sujit
thanks for the quick reaction.
I am thinking about fixing the standard ant <record> task. This way I can get to the SQLUnit results in xml, once it uses the buildloggers.
SQLUnit uses the Ant BuildLogger (specific subclass specified by -logger, not sure if its also a project property). Using the <record> task will actually remove any need for using the <sqlunit> logfile attribute, which also uses the BuildLogger for logging now.
not using the sqlunit/@logfile attribute was my goal anyway ;)
I wanted to have the choice of BuildLogger, so that I can control the output format etc.
Thanks for all your hard work and keeping up with the requests. I havaen't checked out your latest builds but I'll do this ASAP.
Jan