New Year release of 1.23 version of XML2Selenium

Please check what is included into new version of XML2Selenium and switch to it in your development.

1) Modal windows work better now. Framework closes them when test finish. Using <window>  tag now forbidden when you work with modal windows.

2) Added possibility to change variables. Following attributes added: <variable>:

Example:

<?xml version="1.0" encoding="UTF-8"?>
    <!-- Create variable with value 111 -->
    <variable ref="var1" changeable="true" value="111"/>
    <!-- Change value to 555 -->
    <variable change="var1" value="555"/>
    <assert first="${var1}" second="555" action="equals"/>
</test>

You can change variables described above:

<variable ref="var1" changeable="true" value="111"/>
<frame>
    <variable change="var1" value="777"/>
    <assert first="${var1}" second="777" action="equals"/>
</frame>

You can not access variables which described in frame outside this frame:

<frame>
    <variable ref="var1" changeable="true" value="111"/>
</frame>
<variable change="var1" value="777"/>

3) Added feature to break <iterate> loop. Iterate tag now has attribute variableCondition. You can specify variable ref in this attribute. Loop stops if variable is true. If you do not create variable with specified name before, <iterate> does this automatically. If variable with specified name exists, it becomes false when iterate starts.

Example:

<frame ref="breakFrameOnSecondIteration">
    <echo message="${Integer.parseInt(count)+1}"/>
    <variable change="count" 
    value="${Integer.parseInt(count)+1}"/>
    <variable change="condition" 
    value="${Integer.parseInt(count)=4}"/>
</frame>

<iterate for="1,2,3,4,5" variableCondition="condition" 
var="i" run="breakFrameOnSecondIteration"/>

4) Added action getHTML to <webelement>:

Example:

<webelement action="getHTML" xpath="//div[1]" 
returnValueName="html" />

5) Implemented architecture improvements which allow to specify order of plugin calls when some event comes. This improvement allows plugin developers to make more flexible settings.

6) Improved xml validation: if you specify wrong action or attribute value, framework wouldn’t execute test and throws “Parsing error”. Also XSD does not hint some wrong attributes now.

1) NullPointerException, if groovy-variable is not found.

2) Behaviour report is not generated if you specify not exists variable.

3) NullPointerException on linux machines when specify path started from “/” in <property> tag.

4) When change combobox value using <combobox>, onchange browser event wasn’t fired.

5) When test name contains ‘%’ Business and Behaviour reports no displayed correctly. Now ‘%’ is forbidden in test and testcase names.

In order to help you we published in public access a set of report XML2Selenium generates:

Documentation of XML2Selenium

Support services:

Skype: xml2selenium

Email: xml2selenium@jazzteam.org

Site: http://www.xml2selenium.com