The Battery Test System Web UI is highly configurable, both in interface and functionality, through the use of Blazor, C#/.NET, and G Web Development Software plugins that integrators and test engineers can develop.

Plugins provide a means to customize the Web UI environment to meet the needs of each unique test environment. Modular plugins allow you to update the Web UI that end users experience without the need to update to upgrade to new versions of any Web UI software.

There are two general types of plugins for the Web UI:

  • Frontend plugin—Plugin that modifies a user-interactive or visual element of the Web UI; must be developed to produce a working UI appropriate for each unique test environment.

    For example, you can implement things like visualizations, navigable pages, and UI elements.

    Implemented with C# Blazor, G Web Development Software, or HTML.

  • Backend plugin—Plugin that modifies the underlying functionality of the Web UI; may be developed if modifying or supplementing the default functionality of the Web UI is needed.

    For example, you can modify the default storage system the Web UI uses, add custom validation logic for test plans, and identify new types of information to track.

    Implemented with C#/.NET interfaces.

    • Implementing certain behavior with a frontend plugin may require corresponding development of backend plugins. For example, if a type of frontend visualization requires tracking information in the backend that the default implementation does not account for, you will need to use backend plugins to identify the information to track that the frontend can consume to produce the visualization.