Hi, Do you think it's useful to create unit tests with mock or it's better to create just integration tests ? I'm creating tests to activemq-web-console project, but it's harder (at the beginning) to create integration tests instead of unit tests !
Regards, André On Thu, May 5, 2011 at 8:01 AM, André Santi Oliveira <asobra...@gmail.com>wrote: > OK! Thank you guys! > > I totally agree with you about tests then I'll start doing it > as contribution. > > Regards, > André > > > On Thu, May 5, 2011 at 5:50 AM, Gary Tully <gary.tu...@gmail.com> wrote: > >> Great news, welcome on board. >> >> For quick round tripping the mvn jetty:run plugin is a great help: >> >> > cd activemq-web-console/ >> > mvn jetty:run >> > curl http://localhost:8080 or whatever in a browser >> >> There is also a little boot strap class Main.java in the test >> directory that does the same thing from main() but it may need some >> tweeks. >> >> I strongly concur with Johan, tests are king, to both validate and >> protect changes into the future. >> The web-console project could do with some good basic test >> infrastructure, it would be a very welcome contribution. >> >> On 5 May 2011 05:19, André Santi Oliveira <asobra...@gmail.com> wrote: >> > Hi, >> > >> > >> > I'm trying to collaborate with ActiveMQ project; then I've read the >> section >> > "Developers > Building", I've configured my Eclipse environment with >> > ActiveMQ project, but now I need some tips how to be productive. For >> > example, if a change some code in activemq-web-console project, should I >> > execute mvn to recompile the code, after that start ActiveMQ and finally >> to >> > see the changes, or there is a more productive way to do that ? >> > >> > >> > >> > Thanks, >> > >> > André de Santi Oliveira >> > >> >> >> >> -- >> http://blog.garytully.com >> http://fusesource.com >> > >
