unit test

 

Unit Test #: 1
Purpose: To test data type “DATE” in BEA’s Liquid Data database server.
Configuration
Platform:	Windows XP
Database Server:	BEA Liquid Data
Test Data Source:	Test tables have been already set up based on Crystal’s test data. The correctness of the data in the data source has been verified.
Input Data
Automated:	\\shared_drive\unit_test\data_type_tests\testNo1\input.xml
Manually Entered:	(The following information will be typically stored in an xml configuration file if we had this automated).
Input Data Category:	What kind of input data are you going to use test? It should include valid data cases, boundary cases, and negative test cases.
Database Connection String:	…
User ID:	…
Password:	…
Catalog/Schema/Table:	…./…./….
Valid data used for DATE type:	January 1, 2003 December 31, 2003
Boundary data used for DATE type:	January 1, 0999 December 31, 2099
Negative data used for DATE type:	February 31, 2003 88/88/88
Expected Output Condition
Comparison criteria for valid and boundary case data:	The generated report is identical to the same report based on DB2 (or based on ODBC driver to Liquid Data), or the test result xml file is identical to the test result xml based on DB2 (or based on ODBC driver to Liquid Data) Visual inspection of DATE on Crystal report preview.
Pass/Fail criteria for negative case data:	What is the system supposed to with invalid/negative data? Is your code handling the exception properly?
Test Passed/Failed:
Reporting Test Results:

转载于:https://www.cnblogs.com/liushmh/archive/2005/03/15/119319.html