Please check what is included into new version of XML2Selenium and switch to it in your development.
New functional of version 1.35
1) Methods for getting text and HTML content of TinyMCE editor were added in the component for TinyMCE editor of the xml2selenium-helper-lib library.
3) In the field of error in the WebView of Business report the type of exception was removed, only the message was left.
4) WebView was improved. The construction of the path to the failed element and the highlighting of this element in WebView in Business report, if the failed element is situated in <frame> tag which is used in <iterate> tag and is located in the import file was realized.
1) The problem with creating a screenshot and snapshot for <before> and <after> tags under Linux.
2) The problem with creating log files if <test> or <testcase> tag contains a blank name or the name consist of the space in the name attribute.
3) The problem with lighting tests in WebView with partly overlapping names that contain an equals sign ‘=‘, or number at the end of the name.
4) The problem of the same names of import files, which are used in <iterate> tag.
5) While iterating through the list of web elements the frame, embedded in another frame, can not be found if the parent <frame> for <iterate> is situated in the connected import file.
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