|
LoadRunner Results Explorer
This page introduces a client-side desktop program
that scans and opens several drives and folders at a time to
display a table of load test runs created by
LoadRunner during
performance testing.
Get This NowPurchase. When you get our email, right-click and save the .NET assembly to install into your machine. This stand-alone program makes use of Microsoft's .NET 3.5 Framework run-time. The startup program automatically downloads and installs on your computer. Disclaimer: This software is provided "AS IS" with no implied warranty of any kind. The entire risk arising out of the use or performance of the software and source code is with the user. | Topics this page:
|
|
Several Programs for Several Files
To get to all the information that LoadRunner creates during runs, one has to use several programs to open each individual file:
In fact, LoadRunner results physically exists within a hierarchy, each queried using different technologies:
accounts.
|
How My Solution Works (Component Diagram)
This application automatically searches through several drives on several machines to look for LoadRunner run result and associated scenario configuration files. Searching is controlled by search preferences set by each user. This app opens applicable files, analyzes their contents, and displays data found. What is displayed is based on the Display Preference settings of each user. The user can see a list of runs displayed in a timeline graph. Each format displayed can be saved so that a web server can display them publicly on internet browsers. The data displayed can be stored for later comparison. Given enough permissions, a user of this app can copy(archive) and delete(move) LoadRunner run folders. From this app you can select a scenario to open in LoadRuner Load Controller so that you can update configurations to influence future runs. |
REPORT A: Result List View
This app opens the various files associated with a particular run and presents them together, in a set of columns of your chosing.
Click on each button for more information about each column.
|
Search Preferences
Searches can be limited by filters designated by the user (changes to default settings). An industry-standard QBE (Query By Example) format is presented to enter search parameters. The default search for Loadrunner has multiple passes. The first search is for folders containing .lrr (LoadRunner Result files). Regular Expressions can also be specified.
This app opens files in the list of folders found to obtain information about the run encased on each folder. This behavior depends on Display Preferences.
Although this program was written specific to LoadRunner, the design of this program is such that this can be adopted for use with other applications.
|
Display Preferences
This app knows how to present each setting by pre-defined display preferences. For example, a setting recognized as a boolean value is displayed with "Yes" along with value 1 and "No" along with value 0 (zero).
|
REPORT B: Graphic TimeLineThis application presents all runs found on a graphic timeline.
Each dot on the graph represents a run. Navigate through time by dragging on one of the 3 time-resolution bands (day, month, year). The color of icons on the timeline can be set according to a custom set of rules. The timeline is based on an MIT design coded in C#. |
Store for Comparison Report
A separate thread stores what it Data found is stored in an in-memory 3D array. A future version writes to local database using ODBC calls.
|
Saved For Display by Other Programs
|
Options for Development of Desktop ExecutableSeveral tools were considered to develop this app. Adobe AIR, which makes use of Adobe Flash and Flex. Sun Java FX. Microsoft Windows .NET WinForm. Microsoft Windows .NET WinForms VisualWebGUI (from gizmox.com) which can also run webforms apps as Microsoft Silverlight applications on the internet (instead of re-coding in AJAX or other RIA tool). |
Permissions SecurityBecause the whole point of this app is to search through local files, this was built as a desktop executable program that is only reachable when someone gets pass Windows security locking down entry into the machine. Windows also enforces the permissions the user has for reaching other machines. Windows file security enforces what actions a user can perform on specific files and folders. In a corporate setting, a user's permission settings are usually set by placing a specific user within certain group. It is through a group that users obtain permissions. For example, assigning a user to the Administrators group provides that user with permission to do almost everything.
|
Internals: How it works
The application is written in Microsoft's C# programming language, as a client-side assembly This choice came about because of several reasons: To reduce development time several existing libraries are reused by this app:
This program does not read LoadRunner's .eve binary files. To search and examine files, right-click to Save As this .NET assembly to install into your machine. Future interface toward the $39 Universal Explorer Other Columns: |
Generation Log Default Code Generation SettingsDuring each recording, a Generation Log is created with these Code Generation Settings: Section[General]: AlwaysEnableRur=0 AutomaticTitleVerification=0 AutomaticTitleVerificationForEachStep=0 AutomaticTitleVerificationInSeparateSteps=1 AutomaticTitleVerificationUsingURLs=0 CookieExpiration=0 CreateServerFiles=0 CreateServerFilesChangeOriginal=1 EnableHTTPLog=1 ExtendedLog=0 FocusNextElement=0 GenerateScriptComments=0 OutOfContext=0 RRSRemoveZipAndChunkFromResponse=0 RebuildRurDB=0 RurAlwaysCreateNewCfgFile=1 RurCompareBody=0 RurCompareReferrer=1 RurContentTypesList=text/html;text/xml;text/plain;application/x-javascript; RurSimulateCache=0 RurTreatUnhandledReqAsOOC=0 RurUnhandledReq=3 UseFallback=0 UseMixedScript=0 Section[Software\Mercury Interactive\Networking\Multi Settings\SapJS\Recording]: Utf8Support=0
Related Topics:
|