5 Replies Latest reply on Aug 9, 2007 10:44 AM by Dmitriy Lapko

    Slow integration testing suite based on SeamTest - improveme

    Andrei Gh Newbie

      As the framework is designed right now, the embedded server starts for each testing class that extends SeamTest (basically every class that has integration tests using FacesRequest). This is done via SeamTest.init() which is annotated with @Configuration(beforeTestClass=true).

      Starting the server is slow, compared to the duration of the actual test methods, so as the testing suite grows, the developer is encouraged not to run the whole testing suite, which is bad.

      Is there any reason why the server needs to be started for each test class? What would possibly go wrong if server startup (SeamTest.init()) is done only once for all the tests in the suite?