1. Avoid javascript

2. Use the name attribute of the html tags

Hi

i have written a first draft of a outline for the WebTest book. More or less thats what I would like to find in a WebTest book.

0. Preface

A. Functional testing of WEB-Based applications B. Target audience C. How the Book is Organized D. Typographic conventions E. Acknowledgements

I. Introduction

A. Why should we Test? B. What is WebTest? C. History of WebTest D. WebTest's Features E. The components (Ant Extension, Testscript, Testresult File, transformation with xslt, ...) F. How to get WebTest

II. Basic Concepts

0. Difference between Junit Test´s and Function Test´s 1. Inside WebTest 2. How a request is build 3. Verifying the response 4. Closer look at the Resultfile 5. Transformation to HTML with xslt

III. Writing Test

(This Chapter coverage the long way from a single test to a well structured testsuite :) The chapter should also have examples)

1. Installing WebTest (Unix, Windows, ....?) 2. My first test (Rules, Examples, ...) 3. Avoid code duplication (xml- entities, .. ant properties, ...) 4. My first Testsuite 5. WebTest syntax (short reference, see also webpage)

IV. Integration of WebTest in a nightly build

(How we can use WebTest´s in a nightly build Should we describe more the one way (ant, cruisecontrol, maven ?)

1.

V. Customizing WebTest

1. My result page 2. Writing a custom Teststep 3. Debugging WebTest

VI. Developer Information

1. Downloading the source 2. contributions to WebTest

VII. Advanced Topics 1. Testing with proxy´s 2. Firewall 3. Use Advanced Teststeps like ???? 4. Javascrpts 5. Writing language independent test´s VIII. Do´s and don´ts building a testable Web-Application 1. Avoid javascript 2. Use the name attribute of the html tags 3. Use html-buttons

VIII. Complete Reference

(The part of the manual that will have gray borders and be most thumbed through. :-) )

IX. Appendices

A. FAQ?

B. Third-party tools (maven plugin, XPathExplorer, XSLT transformation...) C. Index