[DERBY-4833] Prepare existing JUnit tests for running with automatic index statistics generation

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.8.1.2
• Component/s: Test
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 06/Oct/10 15:59
• Updated: 07/Jul/11 19:15
• Resolved: 07/Jul/11 11:38

Description

During prototyping of a mechanism to create and update index statistics automatically (see DERBY-4771) it turned out that some of the tests fail due to the presence of [improved] index statistics.
Where appropriate the tests should be adjusted to cope with this background activity, and where not appropriate it should be noted such that the feature, when introduced, can be disabled.

As part of this effort I will introduce a utility class for dealing with index statistics in tests. These will be used by some existing tests and also the new tests that will be written for the new feature.

At this point two tests requiring adjustments have been identified (OrderByAndSortAvoidance, UpdateStatisticsTest), and one is under investigation (AutoIncrementTest). More may surface as the work on the feature progress.

Issue Links

• relates to: DERBY-5038 updatelocks test failing in tinderbox when background update statistics are enabled.
• relates to: DERBY-4804 Make database used in store.OSReadOnlyTest fully read-only
• relates to: DERBY-5305 Convert store/updatelocks.sql to JUnit

Sub-Tasks

• Add helper class for working with index statistics in JUnit tests: Closed
• Prepare lang.UpdateStatisticsTest for automatic index statistics generation: Closed