$.udb.benchmark.views

This article is under construction.

Contains view related objects and functions that are accessed via Web Benchmark GUI. The Web Benchmark GUI accesses the $.udb.benchmark API via these views. Every main Web benchmark dialog is constructed via these view objects, they are:

Manage tests
Developer info
Edit actions and parameters
Overview of last test runs
Manage extensions

These views are displayed by triggering their events. The functions they contain are primarily used to construct dialogs so they are not discussed in a wider context.

dev

Description

Displays the “Developer info” dialog, intended for debugging purposes. This view is displayed whenever you press the “Developer info” button.

Example

This example displays the “Developer info” dialog in the web UI:

$.udb.benchmark.trigger(“dev.view”);

edit

Description Displays the “Edit test actions and parameters” dialog,. This view is displayed whenever you press the “Edit” button.

Options

complete: true : Determines whether the dialog is ready for final display or not.

test: null : Opens the dialog of a certain test. Obsolete?]

testId : Opens the dialog of a certain test in case an invoked test is opened. You can locate the testId using $.udb.benchmark.rec.findTest(‘testname’).id

expand: false : Opens the dialog with expanded action rows.

refresh: false : Only refreshes the view contents.

Example

This example displays the “Edit test” dialog in Web Benchmark

$.udb.benchmark.trigger(“edit.view”);

extend

Description Displays the “Manage extensions” dialog,. This view is displayed whenever you press the “Extend” button.

Example

This example displays the “Manage extensions” dialog in Web Benchmark:

$.udb.benchmark.trigger(“extend.view”);

manage

Description Displays the “Manage tests” dialog,. This view is displayed whenever you press the “Manage tests” button.

Options

refresh: false : Only refreshes the view contents
mode: "tests" : Opens the “Manage tests” dialog.

Use the appdata option to open the “Manage application variables” window.

Use the database option to open the “Manage browser database” window.

Example

This example displays the “Manage tests” dialog in Web Benchmark:

$.udb.benchmark.trigger(“manage.view”);

options

Description

Contains default options of certain views as a convenience object. This object is not itself a view.

perf

Description Displays the “Overview of last test runs” dialog,. This view is displayed whenever you press the “Overview” button.

Options

mode: "overview" : Displays the “Overview of last test runs” dialog

Use the tests option together with testId to display the “Test runs for <test>” dialog.

Use runs together with testId and perfRun to display the “Details of test run” dialog.
testId: null : The test to display in case of mode tests. You can locate the testId using $.udb.benchmark.rec.findTest(‘testname’).id

perfRun: null : The run to display in case of mode run. Expects an array of test runs.

Example

This example displays the “Overview of last test runs” dialog in Web Benchmark:

$.udb.benchmark.trigger(“perf.view”);

This example display the Details of test ID 5 , the second run and the fifth:

$.udb.benchmark.trigger(“perf.view”, {mode:”run”,testId:5,perfRun:f“1”,”4”]);

show()

Description The function that prepares a view for displaying. All top-level view events (e.g. edit.view) call this function to prepare a dialog without context. This function in turn calls the view specific show() function, since each view has its own .show() in order to do prepare the view specific content. The actual display is executed by using $.udb.benchmark.dialog

Options

evt: {} : Expects an event object to be passed as input parameter.

options: {} : Additional options to pass on.

util

Description

Contains utility functions and static fields. This object is not itself a view.

Be the first to reply!