TeamDev announces the release of Selenium Inspector, an open source library for simplifying automated testing for Web applications. Selenium Inspector is built on top of the popular Selenium testing framework, and enhances its abilities for component-oriented testing, and simplifies testing of any HTML-based applications as well. Selenium Inspector API allows to create testing solutions for variety of HTML rendering frameworks like JSF component libraries, Spring MVC, Struts, etc. Now web developers can create object-oriented testing APIs for any Web UI library. The Java API for inspecting OpenFaces components is already included. With Selenium Inspector you'll get the following:

• Ability to check actual view of an element style instead of what is declared in CSS but may not be actually applied.
• Specialized higher-level Java API which simplifies inspection not just on primitive elements, but on compound HTML tags, such as ‹table›,‹ul›, etc.
• A wide set of assertion methods for checking actual values of attributes and styles of HTML elements as well as evaluating actual results of client side expressions.
• Selenium Inspector is easy to customize and extend.
• And its free!

Learn more in the product documentation and the product site. If you want to share your feedback, thoughts and ideas, or just need an advice, want to submit a feature request or a bug, you are welcome to contribute and participate!

I get the following error when I tried running the sample code. Do I need setup selenium server explicitly? java.lang.RuntimeException: Can't obtain selenium. SeleniumFactory isn't specified. at org.seleniuminspector.SeleniumHolder.getSelenium(SeleniumHolder.java:37) at org.seleniuminspector.junit4ex.StopBrowserRun.evaluate(StopBrowserRun.java:33) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:44) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:220) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

You have to configure Selenium Factory in order to run tests. Selenium server host, port, browser path, and browser url should be specified at least. Selenium Insector provides SeleniumWithServerAutostartFactory that allows to start selenium server in lazy mode. Please visit updated Developers Guide for more details.

To try the new Selenium Inspector API, I wrote the same program in 3 different ways. Selenium Inspector was easy to use and the nice thing is that you can still use the selenium api along side with the Inspector objects. http://www.vineetmanohar.com/2009/07/29/first-look-at-selenium-inspector/

Is Selenium Inspector available in a maven (maven 2) repository? It would be really helpful if it was. It looks like a great tool and I'm considering using it in our projects here.