The joy of the unexpected – Eclipse, a tool for testers

Session Type: 
Standard [25 minutes]

Schedule info


How did testers use a programmers’ tool – Eclipse for the implementation of web application automated testing? Why was this the best solution? The goal of the session is to provide a closer look into this matter and guide you through a use case and a couple of concrete examples. You will be able to see what obstacles were overcome in order to finish the project successfully.

What was the trigger for this, a bit unusual, solution?
During the development of a complex web application consisting of many web sites that share a common database, one of the major tasks was to implement automated testing. The first step was to find a proper open source tool for automated testing of web applications. There were constraints, such as hybrid (keyword-data) driven methodology support, robustness to successfully deal with a large number of test cases and vast amount of test data, an above all, user-friendliness to software testers who are not experienced programmers. Also, the testing process required all test cases to be managed by test case management tool TestLink and executed, on a daily basis, by continuous integration tool Hudson.
After the intense Internet search, knowledge and experience exchange with colleagues and partnering companies, a non-expected solution emerged – Eclipse, a tool not intended to be used by software testers in their everyday work. Also, it was decided to use automated testing framework for web applications – Selenium and test framework – TestNG.

Solving the puzzle
The main challenge of introducing the testers to Eclipse was the language. To support the difference of conception of Java language abstract concepts between testers and programmers, simplified language was introduced - “Java for Testers”. This language contains only the basic elements of Java and is simple, yet powerful enough to allow testers to easily write and read automated test cases.
After the first step was taken, the problem of creating a link between automated tests and results of its execution to custom made open source test management tool TestLink was solved. With test framework TestNG modifications we were close to the solution.
A custom tool was developed that will extract useful information from automated tests and create files that are readable by TestLink. This tool allowed the testers to maintain traceability between requirements, automated test cases and results of execution.

Complexity of the system under test required building new tools, modifying existing ones, challenging and improving software development life-cycle process.
Eclipse provided the testers with great support in their task. Content assist, refactoring support, code completion and other features helped the testers to work efficiently, while concentrating on the goal rather than on the tool.
Still, implementation of the described solution is a work in progress. Many ideas for improvement are added to road map. Which ones? You can check out if you visit this session.


Thank you for accepting the

Thank you for accepting the proposal.
It is OK to set the talk as a standard talk.


Hi We would like to accept


We would like to accept your talk as a standard talk. (The vast majority of talks will be standard talks) . Please let us know until Friday if this is ok for you.

Thank you