-Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl-Dorg.xml.parsers.sax.parser=org.apache.xerces.parsers.SAXParser 

Siehe dazu auch nur Xerces als Default-Parser setzen. 

"Teflon-Effect": Thoughtworks Time and Expenses System (with Plone). Mercury testing suite (element Selenium protects from Mercury toxity).

Acceptance Testing Tool. Test runs directly in the browser, analysing the DOM. BrowserBot -takes commands and exercises the app as if it was the user.

http://selenium.houghtworks.com

http://www.openqa.org/selenium

Usage

Modes:

TestRunner -put core alongside the app (means static HTML dir).

RemoteControl ("driven mode").

Test cases: Simple HTML tables

| Ignored |

Command | Target | Value

Command | Target |  

Assertion | Expectet | Actual

TestSuites possible.

Understands everthing that can be done by the user and additionally things like changing cookie values.

Concepts

Locators: Find things on the page. id, name, identifier, dom=JS expression

Matching Patterns: glob:pattern, regexp, exact, default is glob

Select: label, value, id, index

Actions: Action, actionAndWait, open

Assertions: Assert, Verify (continue the test in case of a failure), waitFor (e.g. for AJAX – wait until field changes the value)

assertConfirmation: JS confirmation dialog.

Parameters and Variables: store, storeValue, storeText, storeAttribute, stored in JS map storedVars

Variable Substitution – JS Evaluation

Selenium Techniques

Generating UIDs

Creating Test Case JSPs.

Assert sthg not existing. assertXPath extension (on openqa).

Fits into CruiseControl.

auto="true" => /postResults => CC

Remote Control Selenium

Drivers for Java, .NET, Python, Perl, Squeak, and Ruby. Jetty-based proxy-server. Issue Selenium commands – allows to issue all commands via JUnit tests…

Purely declarative Selenium syntax can be broken up.

User-Extensions

user-extensions.js : e.g. own actions. Own locators and assertions (see openqa).

Selenium-IDE

Firefox-Extension. Recorder. With intelligent addons-e.g. forward-engineer macros to remote scripts in all languages.

###XPather + XPath Checker ###

Future

Driver capabilities. 1.0 soon. Documentation for driver. DSL-like language to supplement HTML.

File Uploads possible with Firefox.

Question: What about integration with Fit/FitNesse (e.g. http://www.cornetdesign.com/2006/09/fitnesse-selenium-wrapper.html or http://storytestiq.sourceforge.net/index.html)? Neal Ford didn’t seem to see any use for it as he understands FitNesse also for functional tests and Selenium only for acceptance tests. ###TODO: Send an e-mail  to him###

https-Support (one-time import of the certificate)

(KG’s) Summary

This is "best-of-breed" technology for free. Whoever works in smaller/midrange IT departments and wants to spend money for a commercial tool is going to burn money. The multi-language facility via the remote runner makes Selenium quite adjustable. E.g. the integration with CruiseControl and even JUnit test cases makes it highly valuable.

The Selenium IDE can compete with professional Testing UIs. It’s AJAX support is stunning. Haven’t seen any commercial competitors yet.

]]> http://blog.gresch.de/2007/04/26/jax-2007-testing-with-selenium-neal-ford-thoughtworks/feed/ 3 http://blog.gresch.de/2007/04/24/jax-2007-gwt-creating-ajaxified-web-applications-with-ease-jens-nixdorf-christian-bien-prodyna/ http://blog.gresch.de/2007/04/24/jax-2007-gwt-creating-ajaxified-web-applications-with-ease-jens-nixdorf-christian-bien-prodyna/#comments Tue, 24 Apr 2007 12:23:31 +0000 KG http://web636.webbox122.server-home.org/wpkg/?p=171 Session war auf Deutsch, trotz des Titels.

Teaser: Showcase

Office demo: Mail, Bildverwaltung. Drag'n Drop-Beispiel.

GWT-Konzepte

Motivation – ajaxified -"nicht nur Anwendungen, die AJAX verwenden, sondern RC, desktop-ähnlich".

Neuer Ansatz: Java-only code. Kompiliert zu HTML, JS, CSS. GWT principles.

Components: UI library, Java2JS compiler; Language support < Java 5.

Hosted mode shell. JSNI. XML, JSON support. GWT designer.

Beispiel: Hello World

Project creator script. %GWT_HOME%projectCreator -eclipse GwtHelloWorld

NN 

applicationCreator

Client-Klasse benötigt Client-suffix.

Hosted mode shell.

GwtHello.gwt.xml - Modulbeschreibungsdatei. /public-Verzeichnis enthält statische Elemente. <meta>-Tag in HTML und einbinden der JS-Datei.

Genauerer Überblick

Module

module descriptor, client subpackage (Java client code), public subpackage.

Widgets + Panels

Widgets: Eigentliche GUI-Componenten, listener (Swing-ähnlich?). Panels: Für Anordnung der Widgets. Composites aus mehreren Widgets. Selbsterstellung rein über Java.

RootPanel: Stellt Schnittstelle zu statischen HTML dar. CellPanels, an Swing Layout-Manager angelehnt. TabPanel und StackPanel. PopupPanel, DialogBox. Hyperlink-Panel: Stellt Punkt/Status der App dar (History Funktionsverlinkung nötig).

i18n

Eingebaut – drei Möglichkeiten, lokalized. Klasse pro Sprache. i18nCreator – Script mit Property-Dateien. Interface mit Methode; JavaScript-dynamischer.

RPC-CallsAJAX-calls gewrappt mit RCP-Idiom. Protokoll proprietär, Transport via JSON.

RemoteServiceServlet Implementierung. Servlet-Mapping, URL-Mapping enthält zusätzlich Pfadangabe.

ClientCall-Beispiel. onSuccess/onFailure.

Was kann man transportieren? Primitive, String, Date, alle Arrays der serialisierbaren Typen. LinkedList nicht unterstützt.

Userdefined Types. IsSerializable direkte Implementierung.

In-depth view

Customization

Drei Ansätze:

Ableitungen von UIObjects, Widgets.

Composite von mehreren Widgets.

JSNI – keword native – dann keine Java-Kompilierung. JS-Code darin auskommentiert.

Clientquellcode + Binärkode in jar. Jar im Classpath des GWT-Kompilers. Ggf. Launch-Konfiguration in Eclipse anpassen.

Wichtige Erweiterung: GWT-Widget-Library (Robert Hanson).

Viele interessante Widgets. Ferner: GWTSpringController. Bugfixes.

Evaluierung – Warum und wann an die Nutzung vom GWT denken?

JS und HTML selbst organisieren. Viele Nachteile.

JS Framworks verwenden. Dojo; Scriptaculous/Prototype. Langsam, schwierig, schlecht zu plflegen.

Echo2;

General Interface (Tibco) (+/DirectWebRemoting).

AdobeFlex2 / OpenLaslo/ XUL: Browserunterstützung sehr problematisch.

GWT

contra: Konventionen müssen erst erlernt werden; CSS zur Beschreibung de Widgets. fehlende Unterstützung von 1.5; kein MVC;

pro: In Java verbleiben, also Debugging, Unit-Tests etc. etc.

g4jsf-Integration der Komponenten in JSF.

Attlassian GWTDesigner. "Ohne JS läuft nichts".