https://www.softwaretestingmagazine.com/knowledge/testing-legacy-servers-with-arquillian/ Fri, 08 Jun 2012 21:47:09 +0000 hourly 1 https://www.softwaretestingmagazine.com/knowledge/testing-legacy-servers-with-arquillian/#comment-1005 Fri, 08 Jun 2012 21:47:09 +0000 http://www.softwaretestingmagazine.com/?p=1596#comment-1005 I’ve used Arquillian quite a bit. It started out as a nice tool, after a little learning curve. However, once tests get complex, it becomes a nightmare to maintain. The problem is, that you need to declare your dependencies in your shrinkWrap. This is the code that creates your micro deployment artifact. If you add a dependency to a class (by way of injection, or other means), and that is not included in your shrinkWrap, you have just broken your test. And there’s not clear indication of what the missing dependency is. It can take many hours to try and figure out what broke. I think if this can be made easier, some clear indication of what’s missing, like you get with javac, it would be much better.

]]>