Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
IBM Lotus Domino: Classic Web Application Development Techniques

You're reading from   IBM Lotus Domino: Classic Web Application Development Techniques This tutorial takes Domino developers on a straight path through the jungle of techniques to deploy applications on the web and introduces you to the classic strategies. Why Google it when it‚Äôs all here?

Arrow left icon
Product type Paperback
Published in Mar 2011
Publisher Packt
ISBN-13 9781849682404
Length 344 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Richard G Ellis Richard G Ellis
Author Profile Icon Richard G Ellis
Richard G Ellis
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

IBM Lotus Domino: Classic Web Application Development Techniques
Credits
About the Author
About the Reviewers
www.PacktPub.com
1. Preface
1. Preparation and Habits FREE CHAPTER 2. Design and Development Strategies 3. Forms and Pages 4. Navigation 5. Cascading Style Sheets 6. JavaScript 7. Views 8. Agents 9. Security and Performance 10. Testing and Debugging

Promoting the design from testing to production


An experienced QA Tester can be invaluable to your project. Engage one if possible to challenge your application before you turn it over for customer testing.

Once the application is turned over for customer testing, engage your users early and often to discuss progress and findings. Several customers are better than one. They will discover things you don't find because they will challenge the application in ways you did not consider.

Provide your testers with test scripts and suggestions appropriate to specific design changes or features. Remind them that only after they sign off can the new design move to production.

Use a staging server for user acceptance testing

A staging server should be configured as if it were a full production server. You and your customers should have the same privileges on the staging server as you do on the production server, no more, no less. Identical privileges and conditions will tend to root out many residual...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image