Please check what is included into new version of XML2Selenium and switch to it in your development.
New functional of version 1.22
1) Added new documentation for end user:
- Reference card of XML2Selenium – Short description of all the tags of framework, its attributes and examples how to use. Link: https://docs.google.com/document/d/1hyrt3f20P-rzdvyf1P_hOjCkJ0Z5-Z4ReKcVMGmXT9c/pub
- Interactive manual allowing user to create his first XML2Selenium test step by step easily. And check artifacts and reports XML2Selenium provides. Link: http://xml2selenium.com/guide/
2) In tag <webelement> new attributes added for working with model dialog windows (modal is a windows which blocks work of user with parent window till modal dialog is not closed. Here we mean not div based dialog windows but modal dialogs which are part of html standard):
- showModalDialog – attribute shows that after click modal dialog window is expected to be opened. After that we automatically navigate to that window and its elements. On default value is false.
- closeModalDialog -attribute shows that after clicks modal dialog window is expected to be closed, and focus switched to parent window. On default value is false.
That attribites could be used only with action=’click’. When you are using these attributes your browser window should be active, as Robot library is used.
3) We improved error messages when not valid variable’ names appeared for <variable> tag. It is allowed to use only that symbols for variable names: Latin and Cyrillic letters, numbers, point and underscore.
4) New variables added. They could be used in test, and that provides us with great possibilities:
- ${xml2selenium.suiteId} – unique id for every run of tests by XML2Selenium core. This id is contained in a name of reports’ folder. It is formed on the start of test run using current milliseconds time.
- ${xml2selenium.testCaseName} – full name of test case including packages/folders. Example: basic.testCase1#xml
- ${xml2selenium.date} – current date in the format of dd.mm.yyyy. Examples of date: 02.12.2013
- ${xml2selenium.testName} – name of current test.
- ${xml2selenium.timeStamp} – current time in milliseconds (ms).
5) For tag <assert> new action implemented notEquals. This action checks that two values are not equal to each other.
6) For tag <assert> new action implemented isNotContainsText. It checks that value of first attribute doesn’t contains text of second attribute.
7) In the case attributes 1 or 2 not specified for tag <combobox> now user will be provided with understandable good message.
8) Now in the folders with reports new files added %suiteName%_business_report.htm. That files redirects to the last created reports. Such files added for Business, Behaviour and Technical reports. The purpose is to be able to generate stable links to reports, and share such links between teams.
Examples of links: xml2selenium-testcases/target/xml2selenium/business-reports/FrameworkTest_business_report.htm
Problems fixed
1) We fixed a problem related to the change of bdd messages what it is used in a frame. The purpose is to generate unique and dynamic bdd messages.
2) We have made a fix for attribute message for all the tags. Now it is possible to define own message for all the elements. When something is failed on element this custom message would be shown.
3) Problem with encoding in WebView fixed when cyrillic.
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
