[Db-derby Wiki] Update of "DerbyJunitTestConfiguration" by DanDebrunner

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DanDebrunner:
http://wiki.apache.org/db-derby/DerbyJunitTestConfiguration

------------------------------------------------------------------------------
  http://mail-archives.apache.org/mod_mbox/db-derby-dev/200609.mbox/%3c451C1CDF.7050706@apache.org%3e
  
  Tests can fall into any of the following categories:
-  * embedded & client - runs fixtures in both configurations, some fixtures may only run in a single configuration due to items not supported in a configuration, bugs in a configuration or no value in running the fixture in that configuration.
-  * embedded only - E.g. testing triggers may not provided additional testing by running with the network client
+  * '''embedded & client''' - runs fixtures in both configurations, some individual fixtures with a test class may only run in a single configuration due to items not supported in a configuration, bugs in a configuration or no value in running the fixture in that configuration. Typically tests that are aimed at testing JDBC methods or objects (e.g. functional test packages `jdbcapi` and `jdbc4`) will run in both configurations so that both drivers are tested.
+  * '''embedded only''' - Typically SQL language tests (e.g. function test package `lang`) can run only in embedded since they are testing execution of SQL statements within the embedded engine. For example testing of server side routines, DDL, triggers or GRANT/REVOKE would not gain additional test coverage by running with the client driver. SQL language tests that relate to data types most likely '''will''' benefit from running with the client as well to ensure testing of transmission of the datatype across the DRDA protocol. Test of the storage sub-system (`store` package) most likely will not need to run with the client configuration.
-  * client only - E.g. specific testing of a client data source
+  * '''client only''' - E.g. specific testing of a client data source.
  
  Here are examples of how to write the `suite()` method for the test class `MyTest` for various combinations.
  Any tests that are added into a suite without any client server decorator will run the fixtures only as embedded.