UnitTestDatabaseLogic
Your trail: UnitTestDatabaseLogic

This page (revision-4) was last changed on 07-Oct-2019 18:35 by john  

This page was created on 02-Oct-2019 20:32 by unknown

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

History

Version Date Modified Size Author Changes ... Change note
4 07-Oct-2019 18:35 2 KB john to previous
3 02-Oct-2019 20:39 1 KB john to previous | to last
2 02-Oct-2019 20:34 1 KB john to previous | to last
1 02-Oct-2019 20:32 1 KB unknown to last

Page References

Incoming links Outgoing links
UnitTestDatabaseLogic
UnitTestDatabaseLogic

Difference

Difference between version and

At line 1 removed one line
At line 3 changed one line
Automated/unit/integration testing...Need data setup & teardown.Might be multiple tables with foreign key constraints.  When we insert the data, we'll get new keys, so we need to remember the keys generated.Teardown: might be "delete the data" or might be "just leave it for the next test" or might be "delete SOME of the data" (which might have been generated by the test and not part of the setup).Setup note: if teardown isn't "delete the setup data", then the setup should be more like "find the data from the last test run or create it"."Find the data from the last test run" would probably look like "find config data matching the following list of requirements" (followed by the requirements).Requirements might be: rows having a given set of column values (or ranges of values); related records (e.g., children or parents) have certain column values or cardinalities (no children, exactly one child,2+ kids, exactly n kids, etc.)Setup might be specified as simple column values for rows, with children/related records having FK relationships.OR... might be specified as sproc names with parameter values (e.g., config-writing sprocs). Those sprocs are not under test and are assumed to be working properly. (Although they could have their own associated tests.)
Automated/unit/integration testing...Need data setup & teardown.
Might be multiple tables with foreign key constraints. 
When we insert the data, we'll get new keys, so we need to remember the keys generated.
Teardown: might be "delete the data" or might be "just leave it for the next test" or might be "delete SOME of the data" (which might have been generated by the test and not part of the setup).
Setup note: if teardown isn't "delete the setup data", then the setup should be more like "find the data from the last test run or create it".
"Find the data from the last test run" would probably look like "find config data matching the following list of requirements" (followed by the requirements).Requirements might be: rows having a given set of column values (or ranges of values); related records (e.g., children or parents) have certain column values or cardinalities (no children, exactly one child,2+ kids, exactly n kids, etc.)
Setup might be specified as simple column values for rows, with children/related records having FK relationships.
OR... might be specified as sproc names with parameter values (e.g., config-writing sprocs). Those sprocs are not under test and are assumed to be working properly. (Although they could have their own associated tests.)
This page (revision-4) was last changed on 07-Oct-2019 18:35 by john   Top

About
Help
SysInfo

(page = LeftMenu)

Admin

(page = LeftMenuFooter)

JSPWiki v2.10.2  
JSPWiki v2.10.2