Type: Feature Request
Status: Open (View Workflow)
Affects Version/s: None
Fix Version/s: None
Similar Issues:Show 10 results
ARQ-236 Configure the Container lifecycle based on the Test events ARQ-1358 Define ApplicationContext life cycle events. ARQ-1006 Warp: enriching server-triggered (push/websockets) events ARQ-1103 Event is logged even though it is not executed because observer got unresolvable arguments ARQ-576 The build script bits that downloads and configures 1 or more managed containers should be extracted to a maven plugin, so we don't need to copy paste that logic ARQ-1746 Remove objects (instance, configuration) from Drone events ARQ-654 Change Persistence TransactionStarted event to StartTransaction ARQ-1059 Expose events for instantiation and destruction of drivers ARQ-1472 The precedence for BeforeDroneInstantiated event observation in DroneInstanceCreator is set badly ARQ-151 Containers of same type use same package name
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.
|Field||Original Value||New Value|
|Workflow||jira [ 12434239 ]||GIT Pull Request workflow [ 12444829 ]|