PageRenderTime 18ms CodeModel.GetById 13ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

/tst/org/diffkit/diff/testcase/test22.README.txt

http://diffkit.googlecode.com/
Plain Text | 27 lines | 23 code | 4 blank | 0 comment | 0 complexity | cc376996a21acfe31e5799d0759ae08d MD5 | raw file
 1test22 README
 2=========
 3
 4Description
 5---------- 
 6Demonstrates ability of TestCaseRunner to test for Exceptions (or failures) of 
 7a specified type. In this case, the MagicPlan file specifies displayColumnNames
 8that don't exist in the sources. So we expect that the framework will throw an
 9appropriate exception.
10
11
12Assumptions
13-----------
14- lhs & rhs are DB tables
15- plan file supplies lhs table name and rhs table name
16- plan file supplies ConnectionInfo to H2 DB
17- lhs and rhs tables have identical structure
18- plan file supplies key for ordering the rows
19- plan file specifies displayColumnNames that don't exist in specified sources
20- MagicPlan reverse engineers TableModels from the database
21- MagicPlan construction process validates the displayColumnNames against DB tables
22
23Expectations
24-----------
25- displayColumNames validation fails
26- a DKUserException (end user targeted) is thrown by framework, and caught by TCR
27- message in DKUserException indicates which column names fail validation