During the review for DERBY-1490, several reviewers noted that it would
be useful to be able to run various tests in two configurations:
- with sqlAuthorization=true
- with sqlAuthorization=false
A good example of this is the test suite lang/altertable.sql, which
currently runs with sqlAuthorization=true, but since there are a variety
of different code paths for both sqlAuthorization configurations, it would
be nice if this test suite also ran with sqlAuthorization=false.
How does the new JUnit framework handle this situation? Will this problem
"go away" when all the lang/*.sql tests have been converted to JUnit?
thanks,
bryan