A good idea. I used to have a completely separate project for benchmarks, with an older implementation. I to think these should run nightly instead than continuously and should fail if performance degrades - but at the time I didn't have a CI server.
+1 Il giorno 30/dic/2011 22:58, "Maurizio Cucchiara" <[email protected]> ha scritto: > Personally I like very much junit-benchmark (thanks to Raffaele who > let me know about it), I also understand that accessing to memory > might produce concurrency issues, but I think that integration tests > provide many benefits that unit tests do not (and vice versa). > Moreover, benchmarks are much more expansive in terms of > time/resources consume. > Slow tests give a slow feedback and in the long run might discourage > developers from running tests. > So I'd love to keep them separate and maybe introduce a maven > profile/var to skip benchmarks. > > WDYT? > > Twitter :http://www.twitter.com/m_cucchiara > G+ :https://plus.google.com/107903711540963855921 > Linkedin :http://www.linkedin.com/in/mauriziocucchiara > > Maurizio Cucchiarae >
