Download Redbooks - Lotus software

Transcript
how the match is done aren't important, but if it seems like design replace/refresh isn't
working as you expected, consider the possibility that by renaming a design element, you
have made the design replace process not realize that it's "the same" design element as
before.
Testing the application
For testing, you must have test IDs that represent the different levels of access that user
can have with the application. If you have users the are reader and others can edit, then
you need test IDs with the same access level. Domino has the ability to hide and control
access to everything from the application down to the individual design elements.
The application has to be tested not only for correct functionality but also using the client
application that the end user will be utilizing. Different version of the Notes clients do not
have as much issues as different version of browsers have. Unless this is for internal use
and everyone has the same browser, you have to be able to test the application with a
variety of browsers and versions. There is a few open source tools that can be used for
testing web based applications. The benefit of using these are that you can test overall
functionality very easily and be sure there are no regression issues. Your changes to one
form may cause another form or code to now malfunction.
Testing the entire application for each release can be very time consuming. That is why it
is important to document the changes made in development and build a test case for
those changes. The test case will indicate what functionality the users should see. It
should correspond to the original change or design request. An example is adding a new
form for the user, the design requirements will list the fields and the expected workflow.
The test case would be the steps the user will take to utilize the form and the expected
out come.
Especially for new applications, performance testing under realistic conditions of server
load and number of documents is very important. We very commonly see applications
that worked fine with a few dozen test documents and one user, but once they get tens of
thousands of documents, their performance suffers badly. These problems can be
addressed by following the design principles in the whitepaper "Performance basics for
IBM Lotus Notes developers."
QA to production
When the application has been fully tested, there should have an approval process to
indicate it is ready for production deployment. Provide the template and related
information such as the agents that have to clean up the data, fixes, and so on, to the
production administrator. The Production administrator then do the following:
1. Sign the template using the server's ID or the administrator ID used for signing.
2. Apply the QA template to the appropriate Domino database.
3. Run any update agents that are needed.
4. Enable all scheduled agents.
5. Notify users of updates
56 of 217