Foglight 7.3.0 - Dashboard Support Guide

Drilling Down on Types

The Schema Browser allows you better understand the database schema. Start by selecting a namespace. A namespace is a collection of types that share the same concept. For example, the Administration/Setup & Support/Blackouts namespace contains a group of types that are used to implement blackouts in Foglight. While type names must be unique within a namespace, it is possible to have same type names across multiple namespaces.

Review the list of types associated with the namespace and drill down on a specific type to review its properties, instances, and relationships with other types in the model.

IMPORTANT: The type and collection of available namespaces depends on the range of installed cartridges.

TIP: Another way to drill down on a type is to click a type entry in the Select to Browse list.

IMPORTANT: Selecting a generic type, for example, String, does not show any information about that type in the Schema Browser. The Schema Browser only displays information about Foglight® types.

TIP: Drilling down on a type causes the Schema Browser to refresh and reflect information pertinent to the type. To quickly return to the previous view, use the links in the Recent Selections area.

•

Local Properties and Inherited Properties: Each table shows a list of properties that are local to the selected type (Local Properties) or inherited from a parent type (Inherited Properties). For each property, it indicates if the property is an identity property, and shows its name, description, type name, and non-localized name. Identity properties are indicated with the icon appearing on the left of the property name.

TIP: Use the breadcrumb trail to return to the Schema Browser.

Reporting on Module Unit Tests

The Module Unit Test Report lists the modules that exist in your environment. Each Foglight® module contains a collection of operational elements such as views, dashboards, sub-modules, and other entities. For each module, this dashboard shows the number of functions, queries, along with the numbers and percentages of unit tests defined for the module’s functions and queries.

A unit test is a block of code that can be used to test the logic of a function or a query, to ensure it suits its purpose. Unit tests can detect potential code problems early in the development cycle. The higher percentage of unit tests in a module can prevent unexpected behavior in the application and, as such, improve its reliability.

Drill down on the unit test details to retrieve additional information about a module’s unit test. To publish information about unit tests per module, run a report against one or selected modules using the reporting option from the action panel.

NOTE: The Cartridge Developer role grants access to this dashboard. Your Foglight account must have this role to access this dashboard.

Getting Started

To access this dashboard, on the Development Tools page, click Module Unit Test Report.

Exploring Module Unit Tests Result

If a module includes function of query unit tests, you can drill down on the unit test details to see the unit test details, whether they passed with success, or failed with errors. This information appears in the Module Unit Tests Result view. Display this view by drilling down on Details in the Unit Tests column on the Module Unit Test Report dashboard.

The Module Unit Tests Result view shows how many functions and queries exist in a module, the number of function and query unit tests for that module, the unit test results, and whether unit tests are defined for all functions and queries.

To return to the Module Unit Test Report, use the breadcrumb trail.

If any unit tests result in errors, this is indicated in the Result State column. Clicking this column shows additional information about the error.