Arquillian warp, changing component state during a phase

[anthonyhib]

I want to test some complex navigation rules depending on a component

state, is that supposed to work:

What disturbs me is the method name "verify" + the interface name

ServerAssertion which tend to imply we should not update any server

state there.

     @Test 
     @RunAsClient 
     public void testWin() { 
         Warp.execute(new ClientAction() { 
             @Override 
             public void action() { 
                 browser.navigate().to(deploymentURL + "aPage.jsf"); 
                 WebElement button = 
browser.findElement(By.id("characterGuessForm:submitCharacter")); 
                 // very simple UI interaction 
                 button.click(); 
             } 
         }).verify(new ServerSideAction()); 

         // Assertion on where I am now 
     } 

     public static class ServerSideAction extends ServerAssertion { 

         private static final long serialVersionUID = 1L; 

         @Inject 
        ImportantComponent component; 


         @AfterPhase(Phase.UPDATE_MODEL_VALUES) 
         public void updateComponentState() { 
             component.setXXX("YYY") 
         } 
     } 

[anthonyhib]

answer from Lukas

Hey Anthony,

you can surely modify the server's state from ServerAssertion.

But you must be aware of consequences. :-)

What you have did is completely valid - you modified a bean state in order to influence navigation system.

[lfryc]

Hey Anthony,

this is good point, you can certainly run any action in the verification process which influences state.

Thus it is opening you new options for testing behavior what you would need to "mock" other way otherwise.

However renaming ServerAssertion to ServerAction would imply you expect that implementation will trigger action,

which is kind of strong implication.

Warp.execute(ClientAction).verify(ServerAssertion);

Warp.execute(ClientAction).trigger(ServerAction);

I'm opened to discussion here - what others think about that?

[anthonyhib]

you are right.

However .verify() implies that you only check some states in the Server side.

I don't have the answer

[mkouba]

I think that verify is in fact a kind of action. So if the purpose of renaming is to generalize the meaning it makes sense to me ...