1 Reply Latest reply on Nov 10, 2011 12:25 PM by Alper Akture

    Setting up dependencies in an Arquillian test

    Alper Akture Newbie

      What's the best practice for setting up dependencies in the shrinkWrap? We have many tests, and some tests import many dependencies by both addClass and addPackage. If someone updates a class and adds an injection, or adds same to a class in one of the addPackage dependenies, the tests fail. Is there some approach to minimize the impact of this? The errors messages when running the arquillian tests are sometimes are not very helpful in tracing down missing dependencies. One example:

       

      WELD-001408 Unsatisfied dependencies for type [CurrentMemberFactory] with qualifiers [@Default] at injection point [[field] @Inject private com.ontometrics.readmissions.DefaultReadmissionScoreBuilder.currentMemberFactory]

       

      I've often spent hours tracing down these dependencies to a test that was working, because someone updated. Thanks for any advice.