3 Replies Latest reply on Oct 31, 2007 4:29 PM by timfox

    Microcontainer integration and the test framework

    timfox

      Just a thought:

      The current test framework assumes the various services are MBeans and starts them accordingly.

      When they become POJOs we're going to have to change the framework to use the MC instead.

        • 1. Re: Microcontainer integration and the test framework
          ataylor

          yeah, should make things easier. we can just bootstrap the server.

          • 2. Re: Microcontainer integration and the test framework
            ataylor

            There will be 2 ways to run a server.

            1. similar to how it works now as if it was running within the jbossas using the service container
            2. Bootstrapped standalone directly with just the microcontainer.

            I prefer the second way altho' this doesn't test integration.

            thoughts?

            also, when Tim implements the new persistence mechanism do we really need to run all the tests against every database we support?

            • 3. Re: Microcontainer integration and the test framework
              timfox

               

              "ataylor" wrote:
              There will be 2 ways to run a server.

              1. similar to how it works now as if it was running within the jbossas using the service container
              2. Bootstrapped standalone directly with just the microcontainer.

              I prefer the second way altho'


              Me too.

              this doesn't test integration.


              I don't think that's problem, it's the purpose of the AS integration testsuite to test integration, not our test suite.


              also, when Tim implements the new persistence mechanism do we really need to run all the tests against every database we support?


              No we won't have to This will make life a lot simpler. :)