Please check what is included into new version of XML2Selenium and switch to it in your development.
New functional of version 1.33
1) The ability to declare a <variable> inside the <testcase> tag was added. The variable declared in this way is global and available to all tests of the testcase.
2) The ability to use the <iterate> in <iterate> was added.
Problems fixed
1) Incorrect work of the condition attribute with variables. If the different values of the variable are assigned to the condition attribute of <webelement>, then condition works only with firstly assigned value of the variable, it does not process all other values.
2) <iterate> tag can not find the <frame>, if this tag is declared inside the <frame> tag.
3) Using in the test the <frame> tag with embedded <iterate> from the first import file, this <iterate> tag can not find the <frame> tag from another import file, if these two import files are included in the testcase simultaneously.
4) Incorrect work of isDisplayed, isNotDisplayed actions of <webelement> tag.
5) When an error occurs in the test with several opened windows, <screenshot> and <snapshot> are created for the first opened window, while they should be created for the window in which the error occurred.
You are able to get more information about XML2Selenium if study information below:
In order to help you we published in public access a set of report XML2Selenium generates:
- Master – for product development we have created more than 600 tests and constantly add new. This is done for constant increase of coverage of product functionality. That makes it more stable and reliable. You could study that tests, they contain lots of useful examples.
- SmokeTest – Master always should be stable, but on a practice we always meet fail, error. In order to check different combinations we are supporting special set of tests (near 250) which shows all possible situations – failed tests, validation error and many others. Such build and tests allows us to make manual testing of our product before release. And also it allows us to create automated tests which cover SmokeTest reports. Such automated tests are written on XML2Selenium. Thus we cover own report by own and the same instruments, what means we constantly use XML2Selenium in practice. Please study the tests to understand which error situations could happen.
- SelfTesting – as it was said we are creating tests (now 150) covering our SmokeTest reports. That SelfTesting reports shows result of such tests, and helps us to cover as much as we could of our product with automated tests. This improves automated regression of tests.
- BestPractices – we created these tests especially for you! You are able to study how to work with XML2Selenium, using BestPractices reports and WebView functionality. All the tests are separated on 3 levels: Basic, Intermediate, Advanced. Every level has tests of such types: Basic tasks (everyday routine tasks), Iterative tests (show how to create tests step by step), Product features (shows nice features of XML2Selenium), Popular services (cover Twitter, YouTube and other services), and also WordPress tests (on the example of most popular CMS system WordPress show how to work with concrete product).
Documentation of XML2Selenium
- Full manual
- Reference card
- XSD schema, which required for auto-completion when tests are created
- Interactive guide
- XML2Selenium training video tutorials for beginning users
Support services:
Skype: xml2selenium
Email: xml2selenium@jazzteam.org
