Browse Prior Art Database

Design Element Identifier for Lotus Notes

IP.com Disclosure Number: IPCOM000014974D
Original Publication Date: 2002-Jan-13
Included in the Prior Art Database: 2003-Jun-20
Document File: 1 page(s) / 42K

Publishing Venue

IBM

Abstract

Our experience shows that since Lotus Notes is a Rapid Development type environment, that it may be very difficult to keep design documentation up-to-date. With that in mind, we decided to search out a solution that would allow us to combine black box testing methods with a more "point-in-time" specific content method. Black box testing typically consists of creating and executing test cases based on written documents (usually an External Design Document (EDD) or Requirements document). Our experience has proven that the EDD information is great for creating the test case shells but not for identifying the specific design elements that require functional testing. The TestIt! analysis tool not only allows for the quick and easy creation of functional test cases by design element, but it also allows for revision of test case content following development/test builds. Running an analysis on a Lotus Notes database: The TestIt! Database Analyzer allows a user to get a structured collection of design components and their elements which exist for a given notes database. This compliments the creation for notes database test cases in such a way that test cases can be created for each component and associated elements that exists in a notes database with the design of the database being abstract. How does this make testing production more efficient?

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 1

Design Element Identifier for Lotus Notes

   Our experience shows that since Lotus Notes is a Rapid Development type environment, that it may be very difficult to keep design documentation up-to-date. With that in mind, we decided to search out a solution that would allow us to combine black box testing methods with a more "point-in-time" specific content method. Black box testing typically consists of creating and executing test cases based on written documents (usually an External Design Document (EDD) or Requirements document). Our experience has proven that the EDD information is great for creating the test case shells but not for identifying the specific design elements that require functional testing. The TestIt! analysis tool not only allows for the quick and easy creation of functional test cases by design element, but it also allows for revision of test case content following development/test builds.

Running an analysis on a Lotus Notes database:

The TestIt! Database Analyzer allows a user to get a structured collection of design components and their elements which exist for a given notes database. This compliments the creation for notes database test cases in such a way that test cases can be created for each component and associated elements that exists in a notes database with the design of the database being abstract.

How does this make testing production more efficient?

As developers are implementing the design of a notes database, the required informa...