databene

 
  • Increase font size
  • Default font size
  • Decrease font size

What's new in DB Sanity 0.9.2

Version 0.9.2 brings major enhancements to the generated reports:

  • Tag clouds which provide qualitative (management) overviews at a glance: check and defect domains and check responisibilities
  • A Defects per Tag module which provides the corresponding quantitative information
  • The possibility of defining custom hierarchical check structures by tags with path expressions

Tag Clouds

When the set of checks was restricted by tags, the report displays for which tags checks have been executed, weighted by their frequency - the tag's font size represents the number of checks executed for the tag.

You can configure DB Sanity to use table or author names as tag values automatically by the configuration file dbsanity.xml:

<dbsanity authorInCloud="true" tableInCloud="true">

 

Defects per Tag

In the dashboard view, the 'Defects per Tag' module displays a cloud of the tags for which the most defects have accumulated:

The module's main page displays all tags associated with defective checks in the form of a tag cloud and a list of defect count bars:

 

 

Custom Hierarchical Check Structures

A new service provider interface can be used to induce custom hierarchichal structures:

A custom hierarchy provider must implement the interface org.databene.dbsanity.HierarchyProvider and is activated by the configuration file dbsanity.xml (see the next chapter for an example)

 

Tag-based hierarchical report structures

One HierarchyProvider implementation provided by DB Sanity is the TagHierarchyProvider. Activate it by having the following configuration in your dbsanity.xml configuration file:

<dbsanity>
    <hierarchyProvider spec="new org.databene.dbsanity.hierarchy.TagHierarchyProvider('p')" />
</dbsanity>

Checks which have a tag with a prefix 'p:' are now put together in a tree structure depending on the tags' values which represent paths, e.g. a check with a tag p:person/name is put into a tree node 'name' under a tree node 'person'. Checks without a 'p:' tag are put into the root node.

 

Sub Suite Recursion Depth

The recursion depth of the sub suite lists in the report's dasboard pages is configurable in the dbsanity.xml file:

<dbsanity recursionDepth="1"> 

When using recursionDepth="-1", all sub suites are contained in each super suite's dashboard views.