Test Suite Batch Converter Plugin v1.5 Released

The menu items added for batch conversion

I have released a new version of the Test Suite Batch Converter plugin for Selenium IDE. This version, v1.5, brings the ability to convert test cases directly without requiring them to be part of a test suite via a new menu item “Batch convert test cases”. So now you can convert both test suites and the included test cases using the existing “Batch convert test suites” menu item as well as convert stand alone test cases using the new “Batch convert test cases” menu item.

Along with this, the batch conversion language options (i.e. the formatters) will now be listed in alphabetical order. This version also supports Selenium IDE v1.0.10 and will correctly choose the appropriate file extensions during conversion.

Some interesting things this time included having to make a decision on how to identify that a html file is a test case or not. The parser included in Selenium IDE is very forgiving and treats any html file with table rows as a test case and tries to parse it. Generally, I advise the use of the file extension .sel.htm for test cases. This makes it clear that the file is supposed to be a test case. Alas, such use is not wide spread and hence could not be used. Finally, I had to resort to providing a different menu item for converting just test cases. This way the user has the responsibility to provide valid test cases. This choice also lead to internal refactoring to extract out the common functionality that is now used in two places.

As an aside, the name is no longer accurate, but I have decided not to change it. For those who enjoy the latest cutting edge stuff, you can get it from the versions page on the Firefox addons website. If you want to wait, you will get it automatically as soon as the nice people at AMO approve it. As usual, I would appreciate comments, improvements, advise, criticism, problems… I am still on holiday so responses may be delayed.

This entry was posted in Selenium IDE Plug-ins and tagged , , , , , , , . Bookmark the permalink.

7 Responses to Test Suite Batch Converter Plugin v1.5 Released

  1. Justin Collum says:

    I’d really like to be able to control the file extension of the outputted files.

    • Samit Badle says:


      Is there any specific reason that you would need to change the default extension? For example, changeing the .java extension to something else may not be very useful.


  2. Dan says:

    Thanks for creating this plugin. I am trying to use it to batch convert a large number of test suites and tests (over a thousand tests) to ruby RSpec.

    The issue is about the handling of directory structures. The test suites and tests are in a complex directory structure. The problem is that when I select a test suite (or suites) to convert, the converted suite is fine and has the directory structure preserved. However, the tests wind up being flattened into a single directory. This is causing naming conflicts, etc., and simply put we need the converted tests to be put into a directory structure the same as the one they came from.

    Is there any way this can be fixed?

    (some details – the suites are usually above a folder where the tests are, though the test folders may have subfolders of more tests but no suites – simpleest case is a suite and its tests in the same folder. )

  3. neptune says:

    Just updated to Selenium IDE 1.1.0, and ‘Batch Converter’ disappeared. Thought I’d try to reinstall, but get a failure with message “Requires additional items.” – no mention of which items etc… Thinking this is a general message when incompatibilities exist.

    Will try to roll back to previous IDE, as ‘Batch’ saves me too much work to continue with IDE 1.1.0.

    – neptune

  4. Andy Ballard says:


    Very useful tool, however I do not get a convert to java option…?
    Should I be getting this option in the ‘Batch….’ options?



    • Samit Badle says:

      Hi Andy,

      The recent versions of Selenium IDE have changed the names of the Java formatters. The new names start with JUnit or TestNG and are based on the underlying framework used.


Leave a Reply

Your email address will not be published. Required fields are marked *