Usage

 Prepare TestBench

After installation you can call the portal application TestBench at any time by calling the URL

<server:port>/irj/servlet/prt/portal/prtroot/com.sap.portals.sherlok.TestBench

Then you will see the Main View of TestBench.

 General Operation Overview

You should use two browser windows

There are two ways to start a portal iView in a browser

In the first case you start the iView with fixed parameter set defined in the portalapps.xml file. The better way is to choose the ContentAdministration, because you can enter a well defined parameter set and test your iView with different settings.

Before you start your iView select Reset button of the TestBench. That will clear all values and start the execution. Now repeat the following steps at least 5-10 times

 Example

In the following example TestBench works with the iView Default Framework Page. The iView is called 5 times with the preview function and after each call the NextStep button of the TestBench is pressed. The test uses the testbench.properties file and adds all methods of the package "com.sapportals.portal" as profile points: 

 Preparation

In the ContentAdministration select Default Framework Page:

Open the TestBench in another browser window and press Reset button. Follow the steps


 ProfilePoints

The result is a list of all ProfilePoints with active links for drill down.

 Memory Consumption

If you click on the link in column "CurrSize" for the component TabContentComponent and you get the memory allocation history for this component.

Note: This view shows all memory by your iView and the memory allocated by used services. So you see the memory usage, your iView is responsible for, and not just the memory allocated by the iView itself.

The detail view shows the following entries:
NrGC GC number, i.e. GCs since start of the J2EE server
Total Total memory for the 'scope' after a GC
Allocated Allocated memory for the 'scope' between two GCs
Deallocated Deallocated memory during this GC (again for scope)
TimeStamp Timestamp for the GC (zero for current time)

As result you can see for the component TabControlComponent:

 Time Consumption

If you click on the link in column Name, you get the time measurement for each method of the iView. 

The detail view shows the following entries:
CpuTime Cumulated Time needed by CPU to run this request
Elapsed Cumulated Time elapsed from method entry to exit
NrCalls Number of calls since last reset
Name Name of the method

The component TabControlComponent has three methods and two of them are in the scope of the TestBench timer :