I would suggest that you make sure that your tests are idempotent (http://geekswithblogs.net/dthakur/archive/2004/11/19/15282.aspx) and independent and deterministic. This will not only allow you to run tests in parallel, but it will also help maintainability a lot.
It is also a red flag that you need to cal thread.sleep in your tests. Are you testing multithreaded processes? If to, it is probably better to use thread.wait and thread.notify. John Kramer email: [email protected] mobile: 314.435.2370 skype: kramer.mojiva twitter: @KramerKnowsTech <https://twitter.com/KramerKnowsTech> 0xCAFEBABE00000032 On 9/17/12 10:17 AM, "Hanmay Udgiri" <[email protected]> wrote: >thx guys for your comments.. >yes we have integration tests included in the build. >I have tried running them parallel but the tests are not atomic so are not >working as expected. >we have some DB call where we are using thread sleep,is there anything by >which this can be improved >Also we have any best practices for maven builds. > >Thanks and Regards >Hanmayya > >On Mon, Sep 17, 2012 at 6:48 PM, John Kramer <[email protected]> wrote: > >> I understand your point, and agree that I might be nice to have a bit >>more >> of a standard place for integration tests. However, one point that >>should >> be mentioned is that there are frequently multiple levels of integration >> tests (in container, out of container, ui, etc). Thus it might not be >>so >> simple to just have one spot for integration tests. >> >> John Kramer >> email: [email protected] >> mobile: 314.435.2370 >> skype: kramer.mojiva >> twitter: @KramerKnowsTech <https://twitter.com/KramerKnowsTech> >> 0xCAFEBABE00000032 >> >> >> >> >> >> >> >> On 9/17/12 9:05 AM, "Clebert Suconic" <[email protected]> wrote: >> >> >That's one thing I always thought that maven should have an explicit >> >spot for integration tests. We also had to create a separate profile. >> >Having them into a more standard place would make it cleaner IMO. >> > >> >That's a feature request I know. But does it make sense? >> > >> >Sent from my iPhone >> > >> >On Sep 17, 2012, at 5:39 AM, Barrie Treloar <[email protected]> wrote: >> > >> >> On Mon, Sep 17, 2012 at 5:26 PM, Kristian Rosenvold >> >> <[email protected]> wrote: >> >>> You should probably be looking into parallelizing your tests :) . >> >> >> >> Or looking at what your tests are doing. >> >> 32 minutes sounds like you are doing integration type testing and not >> >> unit tests. >> >> >> >> Pull the integration tests into their own module, which you include >> >> via a profile (e.g. "its"), and get your continuous integration >>server >> >> to run them for you. >> >> The developers can then forget about them until they get emailed >>about >> >> broken builds. >> >> >> >> If they really want to run them, they can just include them via -Pits >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> > >> >--------------------------------------------------------------------- >> >To unsubscribe, e-mail: [email protected] >> >For additional commands, e-mail: [email protected] >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > >-- >Thanks and Regards >Hanmayya Udgiri --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
