Testing if component is NOT present

View: New views
2 Messages — Rating Filter:   Alert me  

Testing if component is NOT present

by Pierre-Yann Bridé :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

Our application create automatically the components. In some case, some
specific components must NOT be created.
How can we test that? If we search for the missing component, the whole
test will fail. If we test by component number,
the test is not failsafe, ie. we want to test the condition that created
the components. If the condition are totaly wrong, the test by number
may not fail.

Any idea?

Pierre-Yann

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: Testing if component is NOT present

by Nobuhiko YASUNAKA :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Pierre-Yann Bridé wrote:
> Our application create automatically the components. In some case, some
> specific components must NOT be created.
> How can we test that? If we search for the missing component, the whole
> test will fail. If we test by component number,
> the test is not failsafe, ie. we want to test the condition that created
> the components. If the condition are totaly wrong, the test by number
> may not fail.

If the created component can be distinguished by it's
name or label, you can use 'if' like this;

<if verifier="Verify" property="name" expected="...."
      isEqual="false"
      componentFinder="COMPONENT_NUMBER" ...  />
</if>


But I see this is too complicated.

--
----------------------------------------------------
Nobuhiko YASUNAKA

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

LightInTheBox - Buy quality products at wholesale price!