Please check what is included into new version of XML2Selenium and switch to it in your development.
New functional of version 1.24
1) We implemented the integration with BrowserStack service, which gives us remote SeleniumRC server suitable for using different Browser and operating system combinations.
For integration new JVM-parameters were added:
- xml2selenium.browserstack.tunnel (true/false) – Able/disable the using Tunneling function.
- xml2selenium.browserstack.debug (true/false) – Able/disable the maintenance of visual test log.
- xml2selenium.browserVersion (String) – Denote the browser version we want to use.
- xml2selenium.osName (String) – Denote the operating system we want to use.
- xml2selenium.osVersion (String) – Denote the operating system version we want to use.
2) We added the new <condition>, tag which is designed to fulfillment or unfulfillment of frame depending on particular conditions.
3) We added the possibility to use Groovy-expression in attribute resource of <import> tag.
4) We added the possibility to open and close at a run a few opened modal windows, i. e. now in test several modal windows could be opened and if we close the second modal window then we automatically return to previous modal window. Also if in test we open several modal windows then at the conclusion of test all modal windows will be closed automatically and the primary window will become active window.
Problems fixed
1) Using two equal names for variableCondition in two tags <iterate>, in the second case variable couldn’t be changed.
2) <iterate> tag is implemented at least once when variableCondition eqals false.
3) NullPointerException, if for <upload> and <variable> tags the attributes weren’t determined.
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
Support services:
Skype: xml2selenium
Email: xml2selenium@jazzteam.org
