Arquillian
  1. Arquillian
  2. ARQ-350

Map client events 1 to 1 with container events

    Details

    • Similar Issues:
      Show 10 results 

      Description

      We should redo how the test execution lifecycles happen. In the current impl the flow is:

      Client(BeforSuite, BeforeClass, Before) -> Container(BeforSuite, BeforeClass, Before, Test, After, AfterClass, AfterSuite) -> Client(After, AfterClass, AfterSuite)

      We should map these 1 to 1 with the incontainer execution and keep the test instance alive between the calls.

      Client(BeforeClass) -> Container(BeforeClass)
      Client(Before) -> Container(Before)
      ..

      This way the execution is closer to how it normally would be, and extensions can interact with the Container/Environment or Client in the appropriate lifecycles more naturally.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Aslak Knutsen
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: